Panel |
---|
...
|
...
|
...
| |||
This is the documentation |
...
for JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, |
...
see our JSU Cloud documentation. |
On this page:
|
Description
The 'Copy ‘Copy Value From Other Field' Field’ post - function copies the value of one field to another field. Since JSU 2.1.0 you You can configure any number of source/destination field pairs.. You can also use this post function to copy from/to comments. The copy operation will can be performed either within the very same issue or to/from some a 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
...
If you are using preconditions with a JSU post function, you can use the following options to define how the precondition is evaluated:
Ignore precondition (default): Every precondition is ignored which means that the post function will always be performed
True: Precondition must be true to execute a post function
False: Precondition must be false to execute a post function
Issue Relation
Include Page | ||||
---|---|---|---|---|
|
Perform As User
Include Page | ||||
---|---|---|---|---|
|
Copy Fields
Include Page | ||||
---|---|---|---|---|
|
Also see See the note about supported field types further downbelow.
Position of the
...
post function
Anchor | ||||
---|---|---|---|---|
|
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
...
‘Create’ transition
The ‘Create' transition is the very fist first transition, which does not yet has 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, 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 |
...
database’. |
...
...
|
...
|
Expand | ||
---|---|---|
| ||
Warning | ||
Exception for
...
Copy Value From Other Field
...
used on
...
the Create transition to populate value from linked issues
Note |
---|
If you are using use the "Copy ‘Copy Value From Other Field" Field’ post function in the Create ‘Create’ transition and you would like to copy values from a 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 , the post function must be placed after 'Creates the issue originally'. An issue has to be firstly first created, then a relation between these linked ticket issues is established and only then values will be properly copied from/to linked issue. |
Any other
...
transition (not
...
‘Create’)
Put 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.
Example
A workflow is configured so that 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.
Supported
...
field types
Include Page | ||||
---|---|---|---|---|
|