The Update or copy field values post function of JWT DC is also available for JWT Cloud (please note the different name 'Update fields'), with minor differences in terms of parameters and options.
The table below shows the detailed mapping between JWT DC and JWT Cloud.
Migration steps
-
Add the Update fields post function.
-
Reconfigure the post function with the help of the following list, providing the necessary basics.
Migration details
Target issue
|
JWT DC parameter options |
JWT Cloud parameter options |
|---|---|
|
Current issue |
Current issue |
|
Parent issue |
Parent issue |
|
Sub-tasks |
Select option Parser expression
Not available in JWT Cloud but you can use a parser expression as described.
|
|
Sibling sub-tasks |
Not available in JWT Cloud.
|
|
Linked issues |
Select option Parser expression
Not available in JWT Cloud but you can use a parser expression as described.
|
|
Linked epic |
Select option Parser expression
Not available in JWT Cloud but you can use a parser expression as described.
|
|
Issues under epic |
Select option Parser expression
Not available in JWT Cloud but you can use a parser expression as described.
|
|
Sibling issues under epic |
Select option Parser expression
Not available in JWT Cloud but you can use a parser expression as described.
|
|
Set target issues manually (parser expression) |
Parser expression
In JWT Cloud, the parser expression has to return an issue key or an issue ID (or a list of them).
|
Fields
Please note that not all fields which can be set in JWT DC are available in JWT Cloud.
The list below shows which JWT DC fields are available on JWT Cloud as well.
|
JWT DC field |
JWT Cloud field |
Notes |
|---|---|---|
|
|
||
|
|
||
|
This field requires a list of IDs of the values to be set. |
||
|
An Atlassian account ID is expected. |
||
|
Attachments (only new attachments will be added) |
n.a. |
If the configuration field value is "Set field value manually (parser expression)", migrate this by selecting "Attachments selected via parser expression" in the Attachments configuration section. |
|
Checkboxes (Custom field) |
This field requires the ID of the value to be set. |
|
|
This field requires a list of IDs of the values to be set. |
||
|
Date picker (Custom field) |
|
|
|
Date Time picker (Custom field) |
|
|
|
|
||
|
|
||
|
Epic link (Custom field) |
|
|
|
Epic name (Custom field) |
|
|
|
This field requires a list of IDs of the values to be set. |
||
|
Group picker (Multiple groups) (Custom field) |
This field requires a list of IDs of the values to be set. |
|
|
Group picker Single group) (Custom field) |
This field requires the ID of the value to be set. |
|
|
Labels (Custom field) |
|
|
|
|
||
|
Number field (Custom field) |
|
|
|
|
||
|
Project picker (Custom field) |
This field requires the ID of the value to be set. |
|
|
Radio buttons (Custom field) |
This field requires a list of IDs of the values to be set. |
|
|
|
||
|
An Atlassian account ID is expected. |
||
|
|
||
|
This field requires the ID of the value to be set. |
||
|
Select list (cascading) (Custom field) |
This field requires the IDs of the values to be set, e.g. |
|
|
Select list (multiple choices) (Custom field) |
This field requires a list of IDs of the values to be set. |
|
|
Select list (single choice) (Custom field) |
This field requires the ID of the value to be set. |
|
|
Sprint (Custom field) |
This field requires the ID of the value to be set. |
|
|
Story points (Custom field) |
|
|
|
Text field (multi-line) (Custom field) |
|
|
|
Text field (single line) (Custom field) |
|
|
|
URL field (Custom field) |
|
|
|
User picker (multiple users) (Custom field) |
A list of Atlassian account IDs is expected. |
|
|
User picker (single user) (Custom field) |
An Atlassian account ID is expected. |
|
|
Version picker (multiple versions) (Custom field) |
This field requires a list of IDs of the values to be set. |
|
|
Version picker (single version) (Custom field) |
This field requires the ID of the value to be set. |
Write protection
-
Write protection is not available.
Additional Options
This parameter is not available in JWT Cloud.
Conditional execution
-
Logical parsing mode
-
Parser expression according to Migrate JWT parser expressions
The list of available field codes differs between JWT DC and JWT Cloud.
Run as
Since only fields containing a user can be selected, the field code from JWT DC may not map to the corresponding field in JWT Cloud.
|
JWT DC parameter options |
JWT Cloud parameter options |
|---|---|
|
A drop down menu where you can select a field (all available Fields are listed) The default is Current user |
The options are equivalent to the ones in JWT DC but split in two separate entries:
The default is the same as in JWT DC: Current user |