Transactions and Issue Management

The atomicity of transactions makes it efficient to implement the integration between AccuRev’s basic version-control facility and its issue-management facility (AccuWork). Suppose a particular AccuWork issue record contains a bug report. When you fix the bug by modifying five files, you’ll want to note this fact in the issue record. AccuRev can simply note the single promote transaction that placed the fixed versions of the five files in the backing stream. Alternatively, you can have AccuRev keep track of the individual versions in the issue record; in this case, the issue record acts as a change package, recording all the versions that were created to implement a particular bug fix or new feature.