| |||||||||||||
Development issues part 2: Bug trackingDevelopment issues part 2: Bug trackingPosted Jan 19, 2008 14:45 UTC (Sat) by fergal (subscriber, #602)In reply to: Development issues part 2: Bug tracking by iabervon Parent article: Development issues part 2: Bug tracking
On the other side, one of the most useful things in resolving a bug is a second report which clarifies or corrects the description of what's actually going on, and this is something that bug tracking systems and triage actively filter out at pretty much all stages. One way to solve this (and several other problems) is to distinguish between bugs and bug reports. I've only ever seen one bug tracker that did this (written for the linux kernel but not adopted). Bugs and bug reports are different concepts and yet all popular bug trackers mush the 2 concepts together, leading crap like "closed as duplicate" and all the pain that comes from that. If you separate the two concepts, then users file reports, triagers either create a new bug or attach the report to an existing bug. Duplicate reports become harmless or even positive if they contain extra info. You can even attach a report to multiple bugs.
(Log in to post comments)
|
|||||||||||||