The Update fields post function automatically updates a single or multiple issue fields on one or multiple target issues.
Additional field values can be inherited or manually set using the JWT expression editor.
The issues to be updated. If a list of issue keys is passed, the update will be performed for every issue in the list.
The following options are available:
When the option parser expression is selected, an expression parser input field is displayed and the input has to be an issue key or an issue list. Every issue in the given list will be updated.
Every supported field can either be set or cleared while transitioning the target issue.
After selecting a field and clicking the Add button, you can select in the popup to set the value in three - or when dealing with selectable fields - four ways:
- Copy field from current issue
- Clear field value
- Set field value manually - Read more about the JWT expression editor
- The option Selected value is available for the following fields types:
- Jira Software related fields like Sprint or Epic
- User related fields like Assignee or Reporter
- Version related fields like Affects- or Fix version/s
- Security level
- and all option based custom fields that are supported
Select the user that will be used to execute the post function. By default, it is set to the current user that executes the transition.
The configured user must have all necessary permissions to update an issue in the configured context as well as to edit all the fields specified.
The result of the logical expression must return a boolean value of either:
true→ the post function will be executed
false→ the post function will not be executed
Using the conditional operator, even complex or multi-layered conditions can be constructed.
Make sure to learn more about defining logical expressions and browse through the various examples here: Logical mode
Use cases and examples
|Use case||Function||Use case description||Complexity|
|Add a sub-task's summary and key to the description of its parent||Update fields|
When a sub-task is created, its summary, issue key and date, and time of creation will be added to the description of the parent issue.
|Assign an issue to the project lead, if the issue is unassigned on creation||Update fields|
When an issue is created without an assignee selected, the issue will be assigned to the project lead of the project.
|Assign an issue to the user who last commented on it||Update fields|
Assign the issue to the user who last commented on the issue.
|Assign important issues to the project lead||Update fields|
Automatically assign and issue to the project lead.
Issues will only be re-assigned if the priority of the issue is set to Highest to make sure that only important issues are being escalated.
|Copy labels of a sub-task to the parent issue upon closing||Update fields||When a sub-task is closed, the labels of the sub-task will be added to the Labels field of the parent issue.|
|Keep parent's priority in sync||Update fields||Set the priority of the parent issue to the priority of the current issue.|
|Set a date field to a future date||Update fields|
Set any date field of an issue to a future date.
|Set Fix version to Affects version when resolving an issue||Update fields|
When an issue is resolved and the resolution set to "Done" the Affects version/s will be added to the Fix version/s field.
|Set the priority to Highest if the 'Infrastructure' component is selected||Update fields|
When an issue is created with the "Infrastructure" component selected, the priority will be set to "Highest".