Skip to end of banner
Go to start of banner

Copy Fields Configuration

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »

You can copy the value of a source field to a destination field. Click the + button to add additional field pairs to your configuration.

Keep in mind that not all conversions from source to destination field are supported, nor feasible. We can only ensure that it will work if the source and destination fields are of the same field type, or the destination field is a text field. Some additional combinations of different field types might work although not officially supported.

Example of copy fields configuration.

Overwrite / append / prepend

For text fields and other fields that can accept multiple values (like checkboxes), you can choose to overwrite, append, or prepend the new value to any existing value. For a text field, you can also choose a separator that is placed between the values (not shown in the screenshot above).

Create version if necessary

Imagine your origin issue has a version that you want to copy to the linked issue. If the destination field is 'Fix Version/s', 'Affects Version/s' or some custom field of type 'Version Picker', you can define that a new version will be created in the target project, if it does not yet exist. If you don't choose this option and that version does not yet exist, the user receives an error message and the transition completes.

A user needs the Administer Projects permission to be able to create a new version.

Create component if necessary

Imagine your origin issue has a component that you want to copy to the linked issue. If the destination field is Components, you define that a new component is created in the target project, if it does not yet exist. If you don't choose this option and that component does not yet exist, the user receives an error message and the transition completes.

A user needs the Administer Projects permission to create a new component.

Special sources

  • *** empty ***:  The destination field will be cleared.

  • *** last comment ***The last comment from the source issue will be copied. In some cases that might be the comment from the transition screen, which the user just entered while performing the current transition.

Special destinations

  • *** new comment *** : A new comment will be created with the copied value. When you choose to overwrite to new comment, a new comment is created, enabling you to add multiple comments in one post function.
    Examples:
    Copy Description to New Comment, overwrite  creates a new comment with the description.
    Copy Summary to New Comment, append with separator ", "  appends the summary to the previously created comment, so the comment will look like <Description>, <Summary>.
    Copy Assignee to New Comment, overwrite → creates a new comment.
    This configuration will result in two comments being created; one with the description and summary, and one with the assignee.

  • No labels