This sounds totally backwards.
It is. It's the result of low level managers using issue counts as KPI: now it's a metric that must be gamed.
The explanation is more prosaic: https://news.ycombinator.com/item?id=17316150
And, the "whole idea" of logging issues is not to see how long they are open for... it's to, you know, log issues, because they can't be fixed instantaneously. Measuring how long they are open for is just a pointy-haired boss side effect, because those are the kind of idiots that would think that kind of metric means anything.
I don't think such cynicism is warranted. Open issue time is a useful metric, at the very least over time, of how quickly developers are fixing problems and how complex they are becoming.
Certainly not something for a pointy haired boss to optimize exclusively for, but a useful bit of data to be taken into consideration with other measurements of performance.
It's not the only factor, it's highly product dependent, but it is very relevant to most outward facing activity...
This is the problem. Why not close them when they are fixed?!?
Not saying this is an excuse, but it's unfortunate reality that "close most issues, see which ones come back" is one of the easier ways to focus on the most important bugs
In many cases, the fix comes from within Facebook or from a different contributor when we/they run into the issue themselves.
> In practice this means that we have issues coming in, but we never close them when they are fixed, causing them to pile up. So we decided that the best thing we could do is mark them as stale and close old issues that nobody has commented on in a while. If we mistakenly closed something that is still an issue, the community will let us know and we can reopen it.
The discussion I had with them was interesting, but it didn't leave me feeling like anything would really change. Seeing your comment reminded me of this and I guess the status quo has remained.
[1] https://ps.reddit.com/r/reactnative/comments/7wqxjy/why_are_...