| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This is the documentation of 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).
...
| Include Page | ||||
|---|---|---|---|---|
|
Issue field values
| Note |
|---|
When defining field values, ensure that the value you enter is valid for the datatype of the selected field. Also verify that the context configuration for the project that uses the workflow will allow the modifying of the selected field. If not, the transition may fail at execution time. |
Typically you will use text or numbers as values.
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:
Vehicles
Car
Train
Bus
Buildings
House
Skyscraper
Using Vehicles as the parameter for Field Value
...
would set the field content to that option; similarly, if you use Train.
Dynamic value macros
If you use
%%CURRENT_USER%%as the field value, the user who triggered the post function will be set as the value.If you use
%%PREVIOUS_USER%%as the field value, the field is updated with the previous user assigned to the field.If you use
%%CURRENT_DATETIME%%as the field value, the current date and time will be set as the value.If you use
%%ADD_CURRENT_USER%%as the field value, the user who triggered the post function will be appended to the existing field content.
| Info |
|---|
Obsolete since JSU version 1.4.10: Please use the option 'Append value' combined with the macro '%%CURRENT_USER%%' instead. |
Position of the post function
It is important to place the post function in the correct order of other post functions.
...
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
| Include Page | ||||
|---|---|---|---|---|
|