This link for reference: open bug list

I was looking through the Stable Releases bug reports and noticed there are currently around 1,500+ open reports (the filter shows 1,569 open items as of today), with some going all the way back to 2018; almost 8 years ago.

Speaking as someone who previously worked as a software developer, that number feels very high for a product that’s actively maintained. I completely understand that Unraid is complex, priorities shift, and resources are finite, this isn’t meant as a complaint or a “gotcha,” more as constructive feedback from a user who cares about the platform.

A few things that stand out to me:

• There are open reports on releases that are many years old and no longer generally available.

• From the outside, it’s hard to tell which of these are:

  • already fixed in newer versions

  • no longer reproducible

  • low-priority but still valid

  • never going to be fixed / effectively “won’t fix”

When a bug list accumulates eight years of open reports, it can give the impression (fairly or not) that the tracker isn’t being actively curated. That can be a bit discouraging for people filing new reports, because it starts to feel like their issues might disappear into a pile that’s too big to ever be addressed.

Would it be possible to do some kind of backlog cleanup / triage pass? For example:

• Auto-close or archive reports that only apply to EOL / unsupported versions, with a clear status like “Archived, please re-test on current release.”

• Ask for re-validation: leave a comment on older reports asking the reporter (or community) to confirm whether the issue still occurs on the latest stable; close if there’s no response after some period.

• Use more explicit statuses/labels (e.g., “Needs info”, “Duplicate”, “Won’t fix”, “Fixed in X.Y.Z”) so the community can see what’s actually still actionable.

• Maybe even publish a brief policy on how old bugs are handled, so expectations are clear

I want to stress: this is coming from a place of respect for the work you’re doing and appreciation for Unraid. The product is great, which is exactly why seeing such a large, long-lived backlog feels a bit crazy to me.

Thanks for reading, and I’d genuinely be interested to hear how the team is thinking about bug triage and whether there are ways the community can help (e.g., re-testing old reports on current releases).

Just my two cents from an ex-dev who’s wrestled with bug backlogs before.

Edited December 4, 2025Dec 4 by TrevP

Yeah, that bug report database needs a good cleaning, I believe that LT plans to have a new bug report tool up soon; that one is very limited since it was adapted from the available forum software functionalities.

It's still the best place to post new bug reports for now, and I and other mods do our best to close solved bugs, and make sure LT is aware of new ones. Also, many users create bug reports for general support issues, which doesn't help, but hopefully there will be a better and actively maintained place for that in the near future.