4 ms·

"If you look around and everything is on fire and your application seems to be about to collapse into the sea AND you produce a graph like this from your tracke

"If you look around and everything is on fire and your application seems to be about to collapse into the sea AND you produce a graph like this from your tracker, it's a sign of a real problem that needs to be dealt with right away." Would be a clear indication that this isn't the heathy version that you describe but rather the unhealthy version the author suggests. At some point your bug tracker becomes noise and you just never deal with it. I have seen it happen, and cleaning it up is a whole separate set of pain.

harryf 11y ago
> At some point your bug tracker becomes noise and you just never deal with it. Judging from the graph it looks like Jira is the tracker in this essay. There's so much horrible UX in Jira it's very likely to be part of the problem. Coping with any volume of bulk data in Jira is a nightmare - for a PM or engineering manager you end up having to most of the prioritization in your head. I'd like to see issue tracking tools on the market that take what we've learned about data visualization in fields like data journalism. Some of the UI elements of OpenRefine, for example, would be huge step forward