This post function is used to update one or multiple issue fields in linked issues or sub-tasks. 


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

By default, only linked issues will be updated.

If you want to also update (sibling) sub-tasks, the specific checkbox in the "Additional options" section has to be checked.


Configuration

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

OptionDescription
AutomaticThis option is only available for the field Assignee.
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)

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

Write protection


Use any of the following filters to refine which issues will be updated.

Filter by project

Filter your project by choosing from one of the following options:

OptionDescription
Any projectThis is the default. If selected, the projects the linked issues belong to do not matter.
Current projectIf selected, only linked issues which belong to the same project as the current issue will be updated.
Any but current projectIf selected, only linked issues which do not belong to the same project as the current issue will be updated.


Filter by link type

Only issues linked to the current issue by the selected link types will be updated. This field is required.

Filter by issue type

Optionally limit the issues to be updated by their issue type.

Filter by status

Optionally limit the issues to be updated by their status.

Filter by field value

Optionally limit the issues to be updated by their field values. To achieve this you must enter an expression in Logical mode. The expression must return  true or false. 

Examples: 

ExpressionDescription


%{seed.issue.assignee} != null


This expression ensures that unassigned issues will not be updated. 

Values in linked issues or sub-tasks have to be referenced by their seed field codes.



%{issue.dueDate} <= %{seed.issue.dueDate}


This expression ensures that the due date of the linked issues is equal or later than current issue's due date.

Values in linked issues or sub-tasks have to be referenced by their seed field codes.




The single filters are AND concatenated. In order for the operation to be successful and update the issues all filter criteria must be met.



The following options are available:

OptionDescription
Update sub-tasks matching the specified filter criteria

Check this option if you also want to update sub-tasks matching the specified filter criteria. This option only makes sense when the current issue itself is not a sub-task.

Update sibling sub-tasks matching the specified filter criteria

Check this option if you also want to update sibling sub-tasks matching the specified filter criteria. This option only makes sense when the current issue itself is a sub-task.

Update recursively linked issues or sub-tasks matching the specified filter criteria

By default JWT will only update directly linked issues or sub-tasks directly under the current issue. If you check this option, recursively linked issues or sub-tasks (e.g. which are linked to a directly linked issue) will also be updated independent of the linking depth. 

Each identified issue will only be updated once.


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






Use cases and examples



Tech review

Style guide



Short descriptionUpdate one or multiple issue fields in linked issues or sub-tasks.
Label