As demonstrated by the undermentioned example, it would have use there:
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)
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 إعجابات