| 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
...
| Info |
|---|
The option ID is not the same as a custom field ID. The custom field ID in this example is the ID assigned to the Onboarding Select custom field. Each option configured for the Onboarding Select cascading field is assigned a unique ID. To find an option ID, see Atlassian’s How to find any custom ID to select your preferred method, and then locate the option ID instead of the custom field ID. |
Dynamic value macros
JSU supports dynamic field values to allow you to copy any field value in the origin issue to a target issue. This includes Jira system fields and custom fields.
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. This is valid for single-user picker fields in the ‘Update Any Issue Field’ post function.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.
Referencing issue fields
You can reference any issue field using the prefix issue followed by the field name, for example, %%issue.assignee%% or %%issue.Labels%%.
...
.
| Info |
|---|
Obsolete since JSU version 1.4.10: Use the option 'Append value' combined with the macro '%%CURRENT_USER%%' instead. |