This post function automatically updates a single or multiple issue fields on a single or multiple target issues.

Additional field values can be taken over or dynamically set using parser expressions. 

If used in the create transition, they need to be placed after the “Create issue initially” post function

Configuration

Target issue

Select the issue(s) to be updated. The following options are available:

OptionDescription
Current issueThe current issue will be updated.
Parent issueThe current issue's parent will be updated.
Sub-tasksThe current issue's sub-tasks will be updated. If you choose this option you can further filter your selection (e.g. by issue type or status). Only useful for standard issues
Sibling sub-tasksThe current issue's sibling sub-tasks will be updated. Only useful if the current issue is a sub-task
Linked issuesLinked issues will be updated. If you choose this option you can further filter your selection (e.g. by issue type or status). 
Linked epicThe related epic will be updated.
Issues under epicAll issues related to the same epic will be updated. If you choose this option you can further filter your selection (e.g. by issue type or status). 
Sibling issues under epicAll sibling issues related to the same epic will be updated. If you choose this option you can further filter your selection (e.g. by issue type or status). 
Set target issue manually (parser expression)

Define the issues that will be transitioned by defining an expression. The JQL mode and Issue list mode are available.

The expression must return either a valid JQL expression or an issue list with issue keys.

Fields

Set or clear values for specific fields. The following options are available depending on the field type:

OptionDescription
Automatic

This option is only available for the field Assignee.

When you select automatic assignment, a user is selected to be assigned based on:

  • The components selected in the issue.

  • The component leads and the assignment policy associated to each component.

  • The project lead (in case no component is selected)

Selected valueSelect a specific value from the dropdown list.
Copy field value from current issueCopy the value from a field in the current issue. Select the field you want to copy the value from.
Set field value manually (parser expression)

Learn more about the possibilities of the JWT expression editor.

Clear field valueChoose this option to clear the value of the target field. This option is not available for the Summary field.

Write protection

Check the write protection option if you want to prevent a field to be updated, if it already has a value. If checked, only empty fields will be set.

Additional options

You have the following two options:

OptionDescription
Send email notification

If you check this option, Jira will send email notifications according to the associated notification scheme.

Update issues immediately

Choose to update issues immediately if you want Jira to fire a separate "Issue updated" event for any field change.  This will also result in a dedicated issue history entry.

Conditional execution

You can optionally specify a logical expression to define the circumstances (or conditions) under which the post function should be executed.

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

Run as

Select which user will be used to execute this post function. By default this parameter is set to the current user. You can also use field codes to run the function as a dynamic user (e.g. current assignee).

Make sure that the user running the post function has all the relevant permissions to perform the actions defined in the configuration (e.g. "Update Issues")!

If you want to keep track the actions being performed automatically, we suggest to create a dedicated JWT account, granted all relevant permissions, and use it in the Run as parameter to identify which changes have been made with JWT.


Use cases and examples


If you still have questions, feel free to refer to our support team.