...
The ‘Copy Value From Other Field’ post function copies the value of one field to another field. You can configure any number of source/destination field pairs. In addition to copying values from fields, You can also use this post function can to copy from/to comments. The copy operation will can be performed within the same issue or to/from some related issue.
...
You must specify the relation between the source and destination issues for the field to copy. Then you can add any number of field pairs to perform the copy operation.
...
Precondition
| Include Page | ||||
|---|---|---|---|---|
|
Issue Relation
| Include Page | ||||
|---|---|---|---|---|
|
Please note that there are also restrictions concerning the post function's position.
Perform As User
| Include Page | ||||
|---|---|---|---|---|
|
Copy Fields
| Include Page | ||||
|---|---|---|---|---|
|
...
Position of the post function
| Anchor | ||||
|---|---|---|---|---|
|
It Jira transitions include essential post functions that are executed in a specific order. When adding JSU post functions to a transition, it is important to place position the post function in the correct order of other with respect to the essential post functions.
...
‘Create’ transition
The Create ‘Create' transition is the first transition, which does not have a source status (only destination status - usually Open, but could also be another).
If you are using add the Copy ‘Copy Value From Other Field Field’ post function in to the Create ‘Create’ transition, in general, you must should generally position it BEFORE before the "Creates the issue originally." and before the "Re-index an issue to keep indexes in sync with the database." ‘Creates the issue originally’ post function.
| Note |
|---|
...
Specific field types |
...
|
...
‘Copy Value From Other |
...
Field’ post function applies to any of the following fields, position it after ‘Creates the issue originally’ and before ‘Re-index an issue to keep indexes in sync with the |
...
database’. |
...
...
|
| Expand | ||
|---|---|---|
| ||
 |
...
| Note |
|---|
If you are using the Copy Value From Other Field post function in the Create transition and you would like to copy values from linked issue (Issue Linking: Issue in Transition = Source, Issue Linking: Issue in Transition = Destination, Parent / Sub-Task, Epic / Issue in Epic), the Copy Value From Other Field" must be placed after 'Creates the issue originally'. An issue has to be first created, then a relation between these linked tickets is established. Only then values will be properly copied from/to linked issue. |
Any other transition (not
...
‘Create’)
Place the Copy ‘Copy Value From Other Field Field’ post function anywhere before the "Update change history for an issue and store the issue in the database." post function.
...
A workflow is configured so the Resolve ‘Resolve’ transition has the 'Copy ‘Copy Value From Other Field' post function. The post function is configured to copy the value of the Assignee ‘Assignee’ field to the TextField 'TextField’ field. If a user resolves an issue on this workflow, the value of the 'Assignee' field will be copied to the 'TextField' field after the issue is resolved.
...