As demonstrated by the undermentioned example, it would have use there:
3 „Gefällt mir“
I’m not sure if that’s a good idea. Ultimately, we as users can’t fix bugs. That can only be done by changing the Discourse code, and that requires a team member to be involved. If that’s not necessary, then Bug is probably not the right category.
I’m concerned that users will mark workarounds as the solution. But then the bug still wouldn’t be fixed. So it would be more confusing than helpful. In your example, the problem isn’t solved either, because there’s already a bug report. I think merging the topics is best in this case. That way, all users will be notified when there’s a fix, regardless of which topic they originally followed. Sometimes it makes sense to close one topic with a reference to the other, but then the likes that supported the closed topic are lost which is sad when affected users are determined by likes and replies.
2 „Gefällt mir“
In the Bug category, we just work with the fixed tag instead. A post saying something is a duplicate isn’t really solving anything, despite being useful, so I don’t think it would have been a good use there either.
Now, why we use fixed in some categories, and the solved-plugin in others, I think that’s probably due to what Moin already said. Tags are a bit more strict in use, so only the team can decide when something is fixed.
3 „Gefällt mir“
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.