3 ms·
Because if they’re not resolved yet, there’s no client suffering from them in short term. If they suffer from such a bug, someone will raise it again.
by rad_gruchalski 4y ago
Because if they’re not resolved yet, there’s no client suffering from them in short term. If they suffer from such a bug, someone will raise it again.
- speedgoose 4y agoUsers don't always complain, they sometimes simply go away.
- rad_gruchalski 4y agoSame outcome, no user to complain. When/if the bug reappears, it is reported again.
- KingOfCoders 4y agoIf an organisation is not willing to fix the bug, the customer will go away, if you have the bug in your bugtracker or not. Bugs in a bugtracker are not important. Fixed bugs are important. There is a distinction. Bugs in a bugtracker that are not fixed get you nowhere.
- KingOfCoders 4y ago"And so are unfixed ones! I'd say even more so." It's better to not fix bugs than to fix them? "But the worst thing is to pretend the problem doesn't exist" No where did I pretend the problem does not exist. I wrote "and we implement ways to not reach high bug levels again" to fix the problem. I'm not advocating slashing all the bugs every month, or every year. I propose slashing bugs once when the reports got out of hand because of a bad bug culture and then implement better QA and bug fixing practices. This is the opposite of what you imply.
- gspr 4y ago> Bugs in a bugtracker are not important. Your customers must be reeling at this! Do you really not think it's important to them that known flaws in the product are documented? > Fixed bugs are important. Sure. And so are unfixed ones! I'd say even more so. > Bugs in a bugtracker that are not fixed get you nowhere. Of course they do! The best thing, as you say, is to fix the problem. But the worst thing is to pretend the problem doesn't exist – documenting it is clearly better.
- gspr 4y ago> Because if they’re not resolved yet, there’s no client suffering from them in short term. This seems like an unrealistically perfect product. > If they suffer from such a bug, someone will raise it again. And this seems terrible for everyone involved. Terrible for the customers who have to nag, stay "on the ball" and make sure bugs get re-filed, and terrible for the developers who have to figure out which old (fake-closed) bug reports actually match the new filings.