The problem of bugs that stay stale or seemingly ignored is not unique to Team Stonehearth. It’s a systemic issue you see across software development of all stripes, and it’s largely because some bugs fall into a Technical Debt category that don’t make sense to fix tactically (“Work Smart”, “Fix It Right” etc).
So the problem becomes one of visibility / ticket upkeep at scale (small team vs. hundreds/thousands of ticket updates). Meaning, if the community had enough visibility into root case, commonality between seemingly disparate bugs, and the team’s plans for solving those strategically, then it would reduce a lot of status checking churn or feelings of abandonment.
Does it make sense to leverage Trello for bugs that will be fixed in a more strategic manner?
If in Discourse you grouped strategic bugs into meaningful high level categories, you could then track those categories in Trello much the same way that you track feature roadmap items today. You could also mark these categories as “blocked waiting on feature X, or Alpha X, etc”. Once closed, it would make bulk closing of tickets easier too, “Filter by X Label. Mark all as Resolved”.