Update Any Issue Field Post Function
This is the JSU for Jira Cloud documentation. If you are using JSU on Jira Server or on Jira Data Center, see our JSU Server/Data Center documentation.
Description
The 'Update Any Issue Field' post function updates any field to a specified value after a transition has been completed. This can be a system- or a custom field.
The field can be on the issue in transition(within the same issue) or on a related issue, like a subtask, a linked issue, or an issue within an Epic (during the transition on the Epic).
In addition to setting values to fields, the 'Update Any Issue Field' post function can also add comments.
Want to try a new way of creating this post function?
We’re working to make it even easier for you to build workflow rules with JSU. A simplied version of this post function is available in our Universal Rule Builder – a new editor experience currently in beta.
Configuration
You must specify the field and the desired value. For example:
Precondition
Issue relation
Perform As User
Issue field
Select the field you want to update.
As a destination you also have special options:
*** new comment ***
A new comment will be created with the entered value.
Field value
Ensure that the value you enter is valid for the data type of the selected field. Also verify, that the context configuration for the project using this workflow will allow modification of the selected field. Typically, you will use text or numbers as values. User fields should be set to the account ID.
Spaces and multiple values
To define a string with spaces or to define multiple values, use double quotation marks " " to wrap each value:
"Events team"
"Events" "HR" "Marketing"
Special macros
The following string values will be resolved at execution runtime.
If you use %%CURRENT_USER%% as the field value, the user who triggered the post function will be set as a value.
If you use %%CURRENT_DATETIME%% as the field value, the current date and time will be set as the value.
Examples
Whenever a parent issue is set to 'In Progress' the assignee of all its subtasks could be set to the current user (the one changing the status on the parent).
A developer has fixed a bug and then proceeds in the Jira workflow to the status 'Resolved' (this might be triggered from their code pushed to Bitbucket). The 'Update any Issue Field' now adds the label 'testing-required'. There are also cases when you need a more complex solution. Have a look at Testing and Fixing Bugs.
For more information on how to configure a post function in Jira, see the Jira documentation.