Comment by stubish

Two major problems.

If a team does not have the bandwidth to fix an issue, closing it acknowledges this and doesn't leave people in false hope. Ideally with a status like 'won't fix' to clarify the situation. Users can move on and deal with the reality, perhaps even rally resources if they are in a position to do so, so the issue can be reopened and addressed. Everyone hates it when you get a 'me too' or 'the developers suck' email to a bug opened 15 years ago. The bug is making the world a worse place.

Secondly, the larger the collection of open issues the harder it is to actually triage and manage. There are plenty of projects where everyone would benefit if the issue tracker suffered catastrophic data loss. So many dangling issues in features that no longer exist or are completely unrecognizable, making it impossible to separate the wheat from the chaff. You are in a twisty maze of 30,000 issues, all of them alike. What should I be working on?

Unfortunately, people react to the first reason poorly if their issue gets closed as won't fix. They take it personally and abuse the developers. So we generally don't use won't fix, because of people being hostile. And then triage falls behind. And then you find you have an unmaintainable bug database of 30,000 open issues, un-triaged, many duplicated, unknown how many actionable. 'open' status has become the unofficial 'wont fix'. When you submit a new bug, you hope someone is watching and you get lucky and someone assigns it 'in progress' or sticks it on a task list. The bug tracker gets bypassed, with real issues going via back channels to developers. The project realizes it has a problem and makes it harder to submit bugs, in a hope they can get on top of things.