The Update linked issue or sub-task post function of JWT DC is also available for JWT Cloud, with minor differences in terms of parameters and options.
The table below shows the detailed mapping between JWT DC and JWT Cloud.
Migration steps
-
Reconfigure the post function with the help of the following list, providing the necessary basics.
Migration details
Fields
The following list shows which JWT DC fields are available on JWT Cloud as well.
Please note that not all fields which can be set in JWT DC are available in JWT Cloud.
|
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. |
||
|
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. |
One key difference between JWT DC and JWT Cloud is that JWT Cloud uses IDs to set fields like checkboxes, versions, and select lists. In these cases, you must:
-
choose the respective ID field from the fields offered by the field code injector (please note, that this value is already set as the default when choosing the option "Copy field value from...") or
-
write a parser expression which returns the ID of the value which shall be set when choosing the option "Set field manually (parser expression)". For single values just enter the ID, e.g.
10001, for lists enter the list of IDs, e.g.10001,10002,10010
In case of User fields, the Atlassian account ID has to be set.
The table below maps the options for setting individual fields:
|
JWT DC option |
JWT Cloud option |
Notes |
|---|---|---|
|
Automatic |
- |
Only available for the field Assignee. |
|
Selected value |
Selected value |
|
|
Copy field value from current issue |
Copy field value from current issue |
Select a field which returns a valid ID of the value which you like to set. The default for the field to be set is preselected (e.g. if you want to set the field Affects version/s, the field Affects version/s ID is preselected). |
|
Set field manually (parser expression) |
Set field manually (parser expression)
|
In JWTC the parser expression has to return the ID of the value which has to be set (in JWT DC it's the value). In case of field codes, you can just add .id to the field code in order to receive the respective id, e.g. The list of available field codes differs between JWT DC and JWT Cloud. |
|
Clear field value |
Clear field value |
|
Filter
|
JWT DC parameter options |
JWT Cloud parameter options |
|---|---|
|
Filter by project |
Filter by project |
|
Filter by link type |
Filter by link type |
|
Filter by issue type |
Filter by issue type |
|
Filter by status |
Filter by status |
|
Filter by field value |
Filter by field value
The list of available field codes differs between JWT DC and JWT Cloud. |
Additional Options
|
JWT DC parameter options |
JWT Cloud parameter options |
|---|---|
|
Update sub-tasks matching the specified filter criteria |
Update sub-tasks matching the specified filter criteria |
|
Update sibling sub-tasks matching the specified filter criteria |
Update sibling sub-tasks matching the specified filter criteria |
|
Update recursively linked issues or sub-tasks matching the specified filter criteria |
- |
|
Send email notification |
- |
|
Update issue immediately |
- |
Conditional execution
The list of available field codes differs between JWT DC and JWT Cloud.
-
Logical parsing mode
-
Parser expression according to Migrate JWT parser expressions
Run as
Since only those fields can be selected which hold a user it may happen that the field code from JWT DC cannot be mapped to the respective 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 |