This operation serves to set value of a selected field on the new issue. You can add any number of Set configurations.
Click the + Button to add more field settings to your configuration.
Please make sure that the value you enter is valid for the datatype of the selected field. Also verify, that the context configuration for the project using this workflow will allow to modify the selected field. Otherwise, the transition may fail at execution time.
Typically you will use text or numbers as value.
See: Post-Function Concatenation Operations
Cascading Select fields
For Cascading Select fields, you may either use the value of the option you would like to set, or it's id. In either case, no need to specify the parent option. For example:
Using Vehicles as the parameter for Field Value would set the field content to that very option. Same if you would choose Train. Or, assuming 10701 is the ID of House, then the option House will be set.
If you use
as the field value (exactly this, nothing more), the user who triggered the post function will be set as value.
If you use
as the field value (exactly this, nothing more), the current date and time will be set as value.
If you use
as the field value (exactly this, nothing more), the user who triggered the post function will be appended to the existing field content.
Obsolete since 1.4.10: %%ADD_CURRENT_USER%%
Please use the option 'Append value' combined with the macro '%%CURRENT_USER%%' instead.
Select the field you want to update.
Overwrite / Append / Prepend
For text fields and some fields that can take multiple values (like checkboxes) you can choose to overwrite, append or prepend the new value to any existing value. In the case of text field, you can also choose a separator that will be put between the values (not shown in the screen shot above).
Create version if necessary
Imagine your origin issue has a version, that you want to copy to the linked issue.
If the destination field is 'Fix Version/s', 'Affects Version/s' or some custom field of type 'Version Picker', you can choose that a new version will be created in the target project, if not yet existed. If you don't choose this option and that version does not yet exist, the user will get an error message and the transition won't complete.
However be aware, that the version will be created, even if the user does not have the 'Administer Projects' permission. (Normally a user needs that permission to be able to create a new version.)
As source you have some additional options:
- *** default value ***
The default value of the destination field will be set.
- *** empty ***
The destination field will be set with the empty string value. When overwriting a field value, the resulting destination value will be null. When appending/prepending a field value, the resulting destination value will be the concatenation of the existing field value (if any) and the separator. If the intention is to clear the destination field value, then use the JSU "Set Any Field Value" or "Clear Field Value" post-functions. (See: Post-Function Concatenation Operations)
- *** transition comment ***
The comment, which the user entered on the transition screen.
- *** last comment ***
The last (most recent) comment already existing on the issue before the transition was started.
As destination you have some additional options:
- *** new comment ***
Create a new comment with the value from the source field.