VersionLink for Subversion is a tool for development teams to leverage the power of Subversion with ease and flexibility of DevTrack. Using DevTrack's award-winning workflow design tool, managers and team leads can easily model a process to capture any type of development, from AGILE to Waterfall and everything in-between.

At certain stages in this workflow, a change to source code is required.

This solution is ideal for

• Subversion users who want a deep integration with issue and defect tracking.

• Projects who want to accurately track why changes were made to files in the SVN repository.

• Users of Visual Studio who want a seamless integration between Subversion, the Visual Studio IDE, and DevTrack.

• Developers who need to know why something was changed, when the change occurred, and what was affected by that change.

• Development managers who need the ability to control when a change should happen, who is accountable for the change, and how that change will move the project towards completion.

• Users who want see source code artifacts affected by a feature or defect.

Full Subversion Support

• VersionLink allows Subversion users to work in their favorite IDE or SVN client workspace to easily associate their commit operations with DevTrack's issues.

• Supported environments include:

  • Visual Studio

  • Rapid SVN

  • Tortoise SVN

• A platform independent client application gives developers full change-management functionalities tied to their DevTrack workflow.

Introducing and Managing Change in the Workspace

• As developers commit new versions of files, they will be prompted to associate those changes with a flexible tracking entity, called a change.

• This change represents a set of work that the committed code is apart of. A change acts like a glue between two otherwise separate pieces of data: the file affected, and the DevTrack issues associated with the work that lead to those files being changed or created.

Seamless Integration

• Once the change is created, or an existing change selected, a developer can choose which DevTrack issues the files are related too.

• This data is saved in relation to the change inside the DevTrack database. A VersionLink user has access to all issues they own within DevTrack.

• The subproject tree is faithfully translated to VersionLink, and full search capabilities are present.

Intelligent Change Management

• VersionLink also automates the status of DevTrack issues associated with the change.

• A developer never has to leave their IDE in order to mark their work items as complete. Once they are ready commit the code to the SVN repository, VersionLink will perform the check-in operation atomically.

• If any of the check-in operations fails, VersionLink will not update the DevTrack issues or the Subversion repository.

Reporting and Metrics

• This new layer of integration allows management and development teams to see the results of their work items within DevTrack.

• A Subversion tab lists all the changes, source files, and related issues for a single work item.

• DevTrack Reports can be run to show critical information such as the list of files changed for a particular version of the software, the files created to resolve one or more bugs, and many other meaningful elements of data.