Part VII. Issue Management Tools

And Eeyore whispered back: “I’m not saying there won’t be an Accident now, mind you. They’re funny things, Accidents. You never have them till you’re having them.”

“Tiggers Don’t Climb Trees,” The House at Pooh Corner, A. A. Milne

Despite all our best wishes and ardent efforts, bugs remain an inevitable part of the development process. Keeping track of defects, change requests, and tasks in general is a crucial best practice for any development project. All need to be tracked, prioritized, assigned, reviewed, and so on. A good tool facilitates interaction between project managers, testers, developers, and other team members, improves visibility on the current state of the project, and makes the development, testing, and debugging processes go more smoothly.

A good defect tracking system should also integrate smoothly with the version control system and make your life a little easier when it comes to organizing releases. For example, you should be able to indicate which issues were fixed when you commit changes to the version control system, and use this information to generate release notes listing the issues fixed in a particular release. When you commit code changes to your version control system, you should be able to refer to issues in your issue tracking system, and the issues should be updated accordingly. All of these little things make team communication just that much more efficient.

There are literally hundreds of bug tracking applications ...

Get Java Power Tools now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.