| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This is the documentation for JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, see our JSU Cloud documentation. |
...
In the past, users forgot to change the Epic status in time and it was left as
| Status | ||
|---|---|---|
|
Update field on all issues related as
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).
...
See: Post Function Concatenation Operations
Cascading Select fields
For Cascading Select fields, you can either use the value of the option you would like to set, or its ID. In either case, there is no need to specify the parent option. For example:
...
Using Vehicles as the parameter for Field Value would set the field content to that option; similarly, if you use Train.
Dynamic value macros
...
Field reference macros
JSU supports the use of macros to reference data or issue field values when configuring some post functions, for example, Update Any Issue Field, or in the Set and Copy operations for the Create a Linked Issue post function.
Legacy system field references
Support for referencing the Current User, Previous User, and Current Date and Time is provided by using the macro syntax below. You can use only one legacy macro at a time to set or update a field. Legacy macros cannot be combined with the
%%CURRENT_USER%%: The user who triggered the post function will be set as the value.If you use
%%PREVIOUS_USER%%as the field value, the : The field is updated with the previous user assigned to the field. If you use%%CURRENT_DATETIME%%as the field value, the This is valid for single-user picker fields in the ‘Update Any Issue Field’ post function.%%CURRENT_DATETIME%%: The current date and time will be set as the value.If you use
%%ADD_CURRENT_USER%%as the field value, theUSER%%:
The user who triggered the post function will be appended to the existing field content.Status colour Yellow title OBSOLETE
| Info |
|---|
Obsolete since JSU version 1.4.10: Please use Use the option 'Append value' combined with the macro ' %%CURRENT_USER%% ' instead.instead. |
Extended system and custom issue field references
| Status | ||||
|---|---|---|---|---|
|
From version 2.43.0, you can reference any issue field using the prefix issue followed by the field name, for example, %%issue.Assignee%% or %%issue.Labels%%. This syntax can be used in the Update Any Issue Field post function and with the Set and Copy operations for the Create a Linked Issue post function.
Multiple field references
You can provide multiple issue field references using macros, for example, you can update a Description field so that it references %%issue.Approver%% is %%issue.Reporter%% where approver is a custom field. Similarly, you can update a comment field with %%issue.Approver%% update %%issue.Creator%% on change to %%issue.Security Level%%.
| Tip |
|---|
If you need a list of Jira system fields for Jira Server/Data Center, see Atlassian’s Issue Fields and Status. |
Position of the post function
...
If you are using the Update any Issue Field post function in the Create transition, you must put it after the "Creates the issue originally." but before the "Re-index an issue to keep indexes in sync with the database." post function. Depending on the field type, you must add the Store Issue post function after the Update Any Issue Field.
| Expand | ||
|---|---|---|
| ||
 In step 4 the "Store Issue" post function is needed, which you must add manually in the workflow configuration. In our example, we use a Workflow Precondition before the Update any Issue Field post function. |
...
For more information on how to configure a post function in Jira, see the Jira documentation.
Supported field types
...