It amazes me that people writing bug-tracking systems never seem to find all the right points to track.
At The Job, the one we have was written under the (apparent) assumption that nobody ever has more than 1 release stream, where a bug might be present in both streams, and need to be tracked as the same bug, but with different fixes (either due to schedules for the releases, or for differing code in the streams)
So we get a mess of duplicated bugs because each tester thinks of a different way to describe the bug, and can't search for the kindred bug, since it will have a different ID in the other streams
Then the process geeks came along and decided that we could keep all the releases under one bug. Of course, that leads to total confusion about if it's been fixed in any specific stream.
No comments:
Post a Comment