Issue-Based Development

Borland AccuRev's change packages directly tie code changes to the issues they resolve. These issues could be stories, defects, requirements, enhancements, tasks, etc. This flexibility allows developers to easily promote all changes by issue and conversely, back out all changes associated with an issue. Issues can also be instantly moved between releases and streams that aren’t directly related to one another, allowing for a significant level of flexibility in release and sprint planning. SCM solutions managing at the file level create chaos when managing change, and often times end up dealing with bad merges, missing files, and broken builds. AccuRev's Change Packages allow you to manage all changes at the "change" level, including merging.




Change Packages

AccuRev Change Packages are the key to change-based development and requirements traceability. By creating logical groupings of code changes, Change Packages allow developers and managers to work at the process level, not just at the code level.


Traceability at the Change Level

AccuRev enables you and your teams to truly work at the change level. By tying code changes to defects, requirements, or user stories, it allows developers to share only completed issues. The whole team is then instantly updated to allow them to see all code associated with those issues, providing true change-based traceability.

AccuWork Issue Tracking

With AccuWork, the integrated issue-tracking software included in AccuRev Enterprise, teams can easily create and manage issues, and keep track of the code changes associated with an issue.

AccuSync ITS Integrations

The AccuSync API takes issue tracking to an even deeper level. Using either the AccuSync SDK for custom integrations, or one of our partner integrations, development organizations can take advantage of full bi-directional synchronization of issues between their dedicated Issue Tracking System and the AccuReve development environment. This level of integration ensures complete visibility in to the state of code, where that code is, and who is working on it, regardless of where the issue originated.