Combine Your Issue Tracking and Development Tasks Together
Details on how issue tracking tools can be integrated with version control and software development systems.
Issue and task tracking plays an important role in both traditional and agile development environments. To save time, increase coordination, and improve communication, it is beneficial to use a version control system that lets you combine your issue tracking and development tasks together.
A version control system can accomplish this by integrating with third-party issue tracking tools. Such products include VersionOne, Jira, Mantis, Ontime, and DevTrack, among others. A few minor configuration changes are necessary to enable integration; the version control system's documentation should explain this.
Among other benefits, integration of this type allows users to view information from the issue tracking tool without leaving the version control system's interface. It also makes correctly assigning various development tasks less difficult to accomplish.
When you successfully combine issue tracking with development tasks, one benefit is that you can more effectively respond to software "bugs" reported by your clients. Fixing major "bugs" in an agile manner is especially important to maintaining customer satisfaction.
For example: when using the DevTrack tool with the PlasticSCM system, you can add issues from within DevTrack and have them associated with branches in PlasticSCM. DevTrack information on the issues being tracked may be viewed from within the PlasticSCM system.
The necessary steps to set up such integration involve configuration changes on both the server and client computers. The required changes are generally a bit more extensive on client systems, but don't take very long to accomplish on either type of computer.
If your current SCM does not have the ability to work together with the desired issue tracking tools, consider obtaining a new SCM that allows your existing projects to be imported from the previous system. There are many other potential benefits to such an upgrade.
It is possible for issue tracking tools to function under different mode configurations while integrated in this manner, including "Task on Changeset" and "Task on Branch". This determines whether issues/tasks are associated with code branches or changesets.
When selecting a version control system and an issue tracking tool to combine, ensure that they are both compatible with your computer equipment and that the specific versions are designed to work together. Installing an extra plugin may be necessary to complete the integration.
Regardless of whether you apply traditional or agile development methods, it will greatly benefit your efforts to combine issue tracking and development tasks together by using a high-quality version control system which supports this type of third-party tool integration.
Issue and task tracking plays an important role in both traditional and agile development environments. To save time, increase coordination, and improve communication, it is beneficial to use a version control system that lets you combine your issue tracking and development tasks together.
A version control system can accomplish this by integrating with third-party issue tracking tools. Such products include VersionOne, Jira, Mantis, Ontime, and DevTrack, among others. A few minor configuration changes are necessary to enable integration; the version control system's documentation should explain this.
Among other benefits, integration of this type allows users to view information from the issue tracking tool without leaving the version control system's interface. It also makes correctly assigning various development tasks less difficult to accomplish.
When you successfully combine issue tracking with development tasks, one benefit is that you can more effectively respond to software "bugs" reported by your clients. Fixing major "bugs" in an agile manner is especially important to maintaining customer satisfaction.
For example: when using the DevTrack tool with the PlasticSCM system, you can add issues from within DevTrack and have them associated with branches in PlasticSCM. DevTrack information on the issues being tracked may be viewed from within the PlasticSCM system.
The necessary steps to set up such integration involve configuration changes on both the server and client computers. The required changes are generally a bit more extensive on client systems, but don't take very long to accomplish on either type of computer.
If your current SCM does not have the ability to work together with the desired issue tracking tools, consider obtaining a new SCM that allows your existing projects to be imported from the previous system. There are many other potential benefits to such an upgrade.
It is possible for issue tracking tools to function under different mode configurations while integrated in this manner, including "Task on Changeset" and "Task on Branch". This determines whether issues/tasks are associated with code branches or changesets.
When selecting a version control system and an issue tracking tool to combine, ensure that they are both compatible with your computer equipment and that the specific versions are designed to work together. Installing an extra plugin may be necessary to complete the integration.
Regardless of whether you apply traditional or agile development methods, it will greatly benefit your efforts to combine issue tracking and development tasks together by using a high-quality version control system which supports this type of third-party tool integration.
Source...