Handling of unapproved bug reports

Utopian bug reports that are not approved just disappear from the system with no tracking or indication of a decision. From a bug reporter perspective this is very frustrating and seems arbitrary.

It is important to treat user feedback as important and respect the time people put into trying to improve the project. What appears as deleting the bug report might hurt the feelings of the bug reporter who is trying to help. Even if the bug is a duplicate, it does not mean that it was findable and a new bug report with a link to the old one might improve the searching ability over time.

The best outcome for a duplicate or "wont fix" or "not a bug it is a feature" bug report is to keep it open for others to find and have an status outcome posted in the bug report.

In bugzilla, trac, github and every other issue tracker, the handing of bug reports that are duplicate or where the developers.
Sometimes a bug report is not seen as an issue from the owner of the project but the users all agree on an outcome.
You might have a bug that is closed as won't fix but where users all chime in after the fact to petition it's inclusion.

You can argue that the contribution is still found in steem, but that is a second system, we are working on utopian and there should be some way to see my past contributions even unapproved in utopian directly.

So my suggestions are :

1. Your post has been not approved notification. Ability to track unapproved posts them.
2. Clear reason why, who unapproved it, it is not clearly visible right now in utopian.
3. Ability to contest the closure of a bug report.
4. Using of closed bug reports to improve the keyword searching of bugs.

My questions is because it is not clear who has the rights to unapprove a post, let's say I am running an open source project, do I get to unapprove posts in my project ? What is the right and responsibility model?

---

Posted on Utopian.io - Rewarding Open Source Contributors

---