3 ms·

> I just close all bugs older than 6 months [...] everyone feels better immediately I mean, people would feel even better if you just closed all the bugs, righ

> I just close all bugs older than 6 months [...] everyone feels better immediately I mean, people would feel even better if you just closed all the bugs, right? Some of the oldest unclosed bug reports are the most valuable. because they document long-standing pain points. Not that you would know... :-) If there were, say, 300 open bugs, you and 4 other people go through and triage them. ("You get bugs whose numbers are 0 mod 5, I get bugs wholes numbers are 1 mod 5", ... ) Organizing lots of tiny bugs into an omnibus bug is also great if all the tasks can be done at the same time. "OMNIBUS: fix help messages. See.... (list of a dozen old closed bugs)"

KingOfCoders 4y ago
"Some of the oldest unclosed bug reports are the most valuable. because they document long-standing pain points." Say there is a bug, "The line should be 2 em high" and the bug is not fixed for 6+ months, how is this more valuable because it's older? Yes, I would agree with the triage, and do it if possible. If an organisation is unwilling to spend resources to fix bugs, a triage doesn't work. It's the same with this 100 item backlogs, people put things in backlogs at position 20+ that are never developed but suggest they are developed, reducing immediate pain ("No, we're not going to develop this") but trading it for long term pain ("No, it's not in the next Sprint"). Yes, aggregating bugs into an OMNIBUS or aggregating bugs into a feature as requirements is valuable too.
- bee_rider 4y ago
  "The line should be 2 em high" seems more like a feature request or... like just a general whining, than a bug. Your strategy of just closing these is probably valid. But I would call it "closing non-bug complaints which abuse the bug tracker," not slashing bugs. The reason people are so confused here, I think, is because to programmers, bugs are incorrect behavior of the program. These bugs exist whether they are reported or not. Removing bug reports does not remove bugs. In other comments you mention "and we implement ways to not reach high bug levels again." Is it possible that from a programmer's point of view, you are actually enforcing proper use of the bug tracker? i.e., keeping graphic design opinions about line widths out of it.
  - KingOfCoders 4y ago
    "is because to programmers" You might be overgeneralizing, I have been coding for 40+ years, maintained several successful open source projects, fixed many bugs, created even more, wrote bug reports and have a Go IDE open right now.
    - bee_rider 4y ago
      So do you disagree with my definition of a bug?

KingOfCoders 4y ago

"Some of the oldest unclosed bug reports are the most valuable. because they document long-standing pain points." Say there is a bug, "The line should be 2 em high" and the bug is not fixed for 6+ months, how is this more valuable because it's older? Yes, I would agree with the triage, and do it if possible. If an organisation is unwilling to spend resources to fix bugs, a triage doesn't work. It's the same with this 100 item backlogs, people put things in backlogs at position 20+ that are never developed but suggest they are developed, reducing immediate pain ("No, we're not going to develop this") but trading it for long term pain ("No, it's not in the next Sprint"). Yes, aggregating bugs into an OMNIBUS or aggregating bugs into a feature as requirements is valuable too.

bee_rider 4y ago
"The line should be 2 em high" seems more like a feature request or... like just a general whining, than a bug. Your strategy of just closing these is probably valid. But I would call it "closing non-bug complaints which abuse the bug tracker," not slashing bugs. The reason people are so confused here, I think, is because to programmers, bugs are incorrect behavior of the program. These bugs exist whether they are reported or not. Removing bug reports does not remove bugs. In other comments you mention "and we implement ways to not reach high bug levels again." Is it possible that from a programmer's point of view, you are actually enforcing proper use of the bug tracker? i.e., keeping graphic design opinions about line widths out of it.
- KingOfCoders 4y ago
  "is because to programmers" You might be overgeneralizing, I have been coding for 40+ years, maintained several successful open source projects, fixed many bugs, created even more, wrote bug reports and have a Go IDE open right now.
  - bee_rider 4y ago
    So do you disagree with my definition of a bug?