The Send to Issue Command
and "Send to Issue (specifying basis)"
 

Invoking the Send to Issue Command

Specifying the Basis Version of the Change

Using the Send to Issue Dialog

Failure to Modify an Existing Change Package Entry

The Send to Issue command creates or modifies change package A set of entries, each in the form of a basis-version/head-version pair, recorded on the Changes tab of an issue record. The change package records the changes to one or more elements, made to implement the feature or bugfix described in that issue record. Each entry in the change package describes changes to one element: the changes between the basis version and the head version. See patch. entries for one or more elements in one or more issue records. When first created, a change package entry has the same structure as a patch A set of versions of a text-file element -- typically, containing the 'recent changes' made in one workspace. Also, the merge-like operation that incorporates those changes into another version of the same element. See merge, basis version, head version, change package, reverse patch.: the set of 'recent changes' to an element. After subsequent modifications, a change package entry can include a much broader set of changes.

The command has several variants, providing different ways to specify the data to be sent to the change package(s):

Invoking the Send to Issue Command

You can invoke Send to Issue in the following contexts. Note that each context provides access to some, but not all, variants of the command.

Specifying the Basis Version of the Change

In the Send to Issue (specifying basis) variant of the command, you specify the basis version , defining the extent of the change to be sent to the change package(s). After you invoke the command, the mouse pointer changes to . Click the version you wish to be the basis version for the change. (You can press the Esc key at this point to cancel the command.)

The basis version you specify must be an ancestor In the version graph of an element, version A is an ancestor of version B is there is a direct line of descent (possibly including merges) from A to B. See predecessor (or direct ancestor). 'A is an ancestor of B' is equivalent to 'B is a descendant of A'. of the head version. If it isn't, an "Invalid Change Package" error occurs.

Using the Send to Issue Dialog

AccuRev prompts you to specify one or more issue records, in which change package entry(s) will be created or modified. If you've specified one of your AccuWork queries A set of search criteria that selects records from an AccuWork issue database, based on the records' field values. Each AccuWork issue database can have one of its queries designated as the "default query", to be invoked automatically in certain situations calling for the user to specify one or more issue records. as the default query An AccuWork query that you've designated to be executed automatically in certain situations: when you open a new Queries tab; when AccuRev prompts you to specify one or more issue records in a Send to Issue command; when you execute Promote and an AccuRev/AccuWork integration is enabled., AccuRev executes the query and displays the results.

You can select one or more of the issue records:

 

 

 

 

You also have two other options for specifying issue records other than the initial set shown by the dialog::

If you don't have a default query, AccuRev prompts you to type in an issue number (or multiple numbers, separated by SPACEs).

 

 

 

 

 

 

Failure to Modify an Existing Change Package Entry

The Send to Issue command fails if AccuRev determines that an existing change package entry cannot be modified by "adding in" the set of versions you specified. A change package entry must always be expressible as "all the versions between the specified head and basis versions". Here are two situations in which this is not possible:

 

Related Topics