AccuRev can record change package entries automatically, whenever the Promote command is invoked in a workspace. For example, suppose issue record #3 represents a particular bug (and its fix). Whenever a developer promotes one or more versions whose changes address that bug, he specifies issue #3 at a prompt. AccuRev automatically creates a change package entry in issue #3 for each promoted version.
Automatic recording of change package entries is enabled through the change-package-level integration between AccuRev configuration management and AccuWork issue management. For more on both these integrations,
Integrations Between AccuRev and AccuWork on page 94 of the
AccuRev Administrator’s Guide.
Also, you can manually add entries to a change package: right-click a version in the File Browser, Version Browser, or History Browser, and then select the
Send to Issue command from the context menu. The selected version becomes the head version of the change package entry; AccuRev automatically determines the corresponding basis version. As the examples above suggest, AccuRev uses an algorithm that determines the set of “recent changes” to the element, made in a single workspace.
In the Version Browser, a variant command, Send to Issue (specifying basis), enables you to pick the basis version, rather than allowing AccuRev to determine it automatically.
You can also invoke the Send to Issue command on the Changes tab of an issue record. This copies an existing change package entry to a different change package (issue record).