Yeah, that is currently by design, but you're not the first person who dislikes the design. The issue tracker goes to some lengths to be an auditable system, keeping a record of all changes. The typical life-cycle of a issue is that its status moves from open, to resolved, to closed. Resolved is an intermediate state where the resolver asserts that the issue has been dealt with. The system then by default reassigns the issue to the person who opened it. If they agree it has been resolved they close the issue. When the issue is closed, it is still in the database, but is automatically filtered out of most of the default views, so that most users never see it again.
Please try this, and see if it works for you. If not please let us know and we'll consider putting an admin-only command to delete the issue altogether.
In the mean time the only way is to delete the record directly from the database. This is officially unsupported, of course, because you can break the app if you delete db records in ways it doesn't expect, but it is certainly possible. |