My company is looking for a new defect tracking tool. One of the issues I have with the old tool and with the current direction things are going in the search for a new tool is that we have standalone tools that do not play nicely together for our TCM, Defect Tracker, Source Control and Project Management. I know that it is nice to have integration between these systems and those integrations can save time and increase productivity as well as provide useful insight into trends, etc., however I was having trouble articulating what exactly those useful integrations are or could be. The tool we are currently looking at for Defect Tracking is JIRA, which I have read good things about, but it doesn't have any built in integration with TFS, TeamCity or AgileZen which are the other tools we are using. My concern is that if we have a bunch of tools that are not integrated or require additional work to integrate then we are creating more work for ourselves down the road. Is there need for concern? Should I just be happy with standalone tools with no integration, or should I commit time and energy to finding tools that work well together? Any links to data or documents on the subject would be useful to me.
A few good reasons for having integration between these systems that I came up with are:
- Associate a test case failure with a bug, and vice-verse. This allows you to easily see what tests/scenarios are blocked by a particular bug and what bugs are currently blocking a specific scenario.
- Associate a check-in and subsequently a build number with the resolution of 1 or more bugs. Currently, there is a manual process to a) make a check-in, b) resolve one or more bugs, c) include the change-list and build number in each resolved bug.
- Get detailed commit graphs and statistics associated to bug resolutions.
- Report on defects fixed within a build, or between a range of builds.
Any other ideas or additional integrations that are or could be useful?