Copy Fields Configuration
JSU’s Copy Value From Other Field and Create a Linked Transition post functions allow you to define multiple copy value pairs from a source field to a destination field.
Not all conversions from source to destination field are supported, nor feasible. The copy function works if the source and destination fields are of the same field type, or if the destination field is a text field. Some additional combinations will also work, however, they are not officially supported.
Overwrite / Append / Prepend
For text fields and some fields that can accept multiple values, for example, 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 will be placed between the values.
Create version if necessary
If your origin issue has a version, it can be copied to the linked issue.
If the destination field is 'Fix Version/s', 'Affects Version/s' or a custom field of type 'Version Picker', you can choose to create a new version in the target project, if it does not yet exist. If you don't select this option and that version does not yet exist, an error message will be displayed to users and the transition won't complete.
The new version will be created even if the user does not have the Administer Projects permission. (Normally a user needs that permission to be able to create a new version.)
Special 'Sources'
*** default value ***: The default value of the destination field will be set.*** empty ***: The destination field will be set with the empty string value. When overwriting a field value, the resulting destination value will be null. When appending/prepending a field value, the resulting destination value will be the concatenation of the existing field value (if any) and the separator. If the aim is to clear the destination field value, use JSU’s ‘Set Any Field Value’ or ‘Clear Field Value’ post function. (See: Post Function Concatenation Operations)*** transition comment ***: Use the comment that the user entered on the transition screen.*** last comment ***: Use the last (most recent) comment on the issue before the transition was started.
Special 'Destinations'
*** new comment ***: Create a new comment with the value from the source field.*** new internal note ***: Create a new internal note with the value from the source field (Jira Service Management only).
A new internal note is created only for Jira Service Management (JSM) project issues. For non-JSM projects, a regular comment is created with the value from the source field.