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 parser expressions.
Use cases and examples using this post function
|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 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".