...
Info |
---|
Not all conversions from source to destination field are supported, nor feasible. Ensure that 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. |
Excerpt | ||||
---|---|---|---|---|
| ||||
Overwrite / append / prependFor 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 necessaryImagine 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.
Create component if necessaryImagine 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.
Special sourcesIn addition to fields, you can select from the following special sources to copy to a destination issue. For example, you can copy the value of the previous user to the Assignee field of a new issue.
Special destinations
|