4 ms·

Yeah, I've worked in groups like that. Simplicity works great until testers need to verify that the bug was fixed and see the way that the issue was found and

by crusso 14y ago

Yeah, I've worked in groups like that. Simplicity works great until testers need to verify that the bug was fixed and see the way that the issue was found and how to reproduce it or god forbid the developer rationale in what he did. Then rather than looking in an easy to search system or record they're stopping developers from writing code so they can answer the questions. Then as is typical with informal systems, they have those conversations over the phone which means that the knowledge never goes beyond those two people. All these failures just get magnified when the software is then distributed out in the field or new developers join the team down the road.

gcr 14y ago
You can misuse any system. JIRA or BugZilla doesn't magically give the testers that information; the burden is on the developers to document what they did. Personally, as a developer with other things to do, I'd rather just jot my notes in my bugs.txt file instead of remembering to put them in BugZilla's "Steps to reproduce:" text box. I don't understand your point about searchability. It's easier to grep through a text file than remember the proper incantation to go in <random bug tracker package's search box>