| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This is the documentation of JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, see our JSU Cloud documentation. |
Description
The 'Copy Value From Other Field' post-function copies the value of one field to another field. Since JSU 2.1.0 you can configure any number of source/destination field pairs. In addition to copying values from fields, this post-function can also copy from/to comments.
The copy operation will be performed either within the very same issue or to/from some related issue.
Configuration
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 | ||||
|---|---|---|---|---|
|
See the note about supported field types below.
Position of the Post Function
| Anchor | ||||
|---|---|---|---|---|
|
It is important to place the post function in the correct order of other post functions.
...
The 'Create' transition is the very first transition, which does not yet has a source status (only destination status - usually Open, but could also be another).
If you are using the "Copy Value From Other Field" post function in the Create transition, in general, you must position it BEFORE the "Creates the issue originally." and before the "Re-index an issue to keep indexes in sync with the database." post function.
For certain field types (used as source or destination) "Copy Value From Other Field" has to be positioned AFTER "Creates the issue originally." but before "Re-index an issue to keep indexes in sync with the database."
Affected fields are:
Watchers
Labels
*** new comment ***
| Expand | ||
|---|---|---|
| ||
 | title |
Exception for "Copy Value From Other Field" used on create transition to populate value from linked issues
| Warning |
|---|
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) "Copy Value From Other Field" has to 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)
Put the "Copy Value From Other Field" post function anywhere before the "Update change history for an issue and store the issue in the database." post function.
Example
A workflow is configured so that the 'Resolve' transition has the 'Copy Value From Other Field' post-function. The function is configured to copy the value of the 'Assignee' field to the '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.
Supported Field Types
| Include Page | ||||
|---|---|---|---|---|
|