With JSU, you can copy or set field values on issues created through a post function. Typically you will use text or numbers as values.
On this page:
|
Note |
---|
When defining field setting values to fields, 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
...
it’s important to ensure the data you define is compatible with the field type. For example you cannot update a Number field with a text-value, If any configuration is not valid, then JSU will be unable to update the desired issue/s as instructed. |
Cascading select lists
For cascading select lists, you can either use the value (name or number) of the option you would like to set, or its the option ID. In either caseWhen using the value, 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 sets the field content to that option; similarly, if you choose use Train
.
...
Using the option ID for cascading fields
If
...
the set value you define occurs more than once in the cascading select list, use the option ID instead of a name. The option ID lets JSU determine the correct value to assign in the new issue.
Example:
A custom cascading select list called Onboarding Select contains: Marketing
and Onboarding - Marketing
.
...
To use the parent option, Marketing
, enter the option ID of the parent option. Here, the option ID for the parent option is 10200
.
...
In the Set configuration field, enter 10200
then select Onboarding Select.
...
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. |
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%%CURRENT_DATETIME%%
as the field value, the%%PREVIOUS_USER%%
: 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.%%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. |