Thanks for the suggestion! It’s always good to sanity check the way categories are set up so I appreciate you thinking about it and starting this topic.
As Moin and Charlie have pointed out, our team rely on fixed and closing topics (actions only available to us) to communicate with the community that a bug has been, well, fixed! This seems to be working pretty well and is a way for us to keep a fairly obvious backlog of bugs that need fixing.
It’s true that in the bug category a person who is able to provide a solution doesn’t get credit for it in the same way that they would in categories with the solved plugin enabled, which is a pity. In the bug category, the person reporting the bug does get a badge for it if it is liked by a member of the Discourse team. But others helping along the way by providing repro steps, pointing out dupes, suggesting solutions and so on will not get credit. Something to think about.
In this case it would have been nice for you to have been able to credit Moin with pointing out that the report is a dupe, but keeping the topic also creates some extra noise that will make parsing all the open bug reports a bit tricker for the team. So hope you don’t mind but I set a timer to delete it.