When you submit the <modifyIssue> data structure to the AccuWork CLI, it modifies the specified issue record. As when you create a new issue record with the AccuWork CLI, field validations are not applied.
Instead of using a <modifyIssue> document to change an existing issue record, you can use it to create a new issue record. This is useful for copying issue records from one depot to another. For example, you might use a
<queryIssue> document, as described earlier, to retrieve the contents of an issue record from depot
Problems, in the form of an
<issues> document. As described in
Step 3 above, when you change the
<issues> tag to a
<modifyIssue> tag, specify a different depot:
In this example, the issue record will effectively be copied from the Problems depot to the
Problems_Public depot. Make sure the target depot exists and has the same schema as the source depot.
The <modifyIssue> technique is also useful for making copies of the issue records that act as change packages, and for replicating issue records between different AccuRev sites.
Note that a new issue record created with <newIssue> always gets assigned the next available issue number; by contrast, a new issue record created with
<modifyIssue> gets the issue number specified by the
<issueNum fid="1"> subelement: