Migrate 'Update linked issue or sub-task'

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

Add the Update linked issue or sub-task post function.
Reconfigure the post function with the help of the following list, providing the necessary basics.

Migration details

JWT DC parameter

Unknown Attachment JWT DC parameter options

Unknown Attachment JWT Cloud parameter options

Notes

Fields

The following expandable list shows which JWT DC fields are available on JWT Cloud as well.

Fields

Please note that not all fields which can be set in JWT DC are available in JWT Cloud.

Unknown AttachmentJWT DC field	Unknown AttachmentJWT Cloud field	Notes
Summary	Summary
Description	Description
Affected versions	Affects version/s	This field requires a list of IDs of the values to be set.
Assignee	Assignee	An Atlassian account ID is expected.
Checkboxes (Custom field)	Checkboxes	This field requires the ID of the value to be set.
Components	Component/s	This field requires a list of IDs of the values to be set.
Date picker (Custom field)	Date Picker
Date Time picker (Custom field)	Date Time Picker
Due date	Due date
Environment	Environment
Epic link (Custom field)	Epic link
Epic name (Custom field)	Epic name
Fix versions	Fix version/s	This field requires a list of IDs of the values to be set.
Group picker (Multiple groups) (Custom field)	Group Picker (multiple groups)	This field requires a list of IDs of the values to be set.
Group picker Single group) (Custom field)	Group Picker (single group)	This field requires the ID of the value to be set.
Labels (Custom field)	Labels (Custom field)
New labels	Labels
Number field (Custom field)	Number Field
Original estimate (minutes)	Original estimate (minutes)
Project picker (Custom field)	Project Picker (single project)	This field requires the ID of the value to be set.
Radio buttons (Custom field)	Radio Buttons	This field requires a list of IDs of the values to be set.
Remaining estimate (minutes)	Remaining estimate (minutes)
Reporter	Reporter	An Atlassian account ID is expected.
Resolution	Resolution
Security level	Security level	This field requires the ID of the value to be set.
Select list (cascading) (Custom field)	Select list (cascading)	This field requires the IDs of the values to be set, e.g.
Select list (multiple choices) (Custom field)	Select List (multiple choices)	This field requires a list of IDs of the values to be set.
Select list (single choice) (Custom field)	Select List (single choice)	This field requires the ID of the value to be set.
Sprint (Custom field)	Sprint	This field requires the ID of the value to be set.
Story points (Custom field)	Story point estimate
Text field (multi-line) (Custom field)	Text field (multi-line)
Text field (single line) (Custom field)	Text field (single line)
URL field (Custom field)	URL Field
User picker (multiple users) (Custom field)	User Picker (multiple users)	A list of Atlassian account IDs is expected.
User picker (single user) (Custom field)	User Picker (single user)	An Atlassian account ID is expected.
Version picker (multiple versions) (Custom field)	Version Picker (multiple versions)	This field requires a list of IDs of the values to be set.
Version picker (single version) (Custom field)	Version Picker (single version)	This field requires the ID of the value to be set.

Please find in the table below the mapping of the options for setting individual fields:

One important difference between JWT DC and JWT Cloud is that JWT Cloud uses IDs when setting fields like Checkboxes, Versions, Select lists etc. In those cases you have to care for

choosing 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
writing 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 above shows in the Notes which fields are concerned.

Unknown AttachmentJWT DC option	Unknown AttachmentJWT 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) General parsing mode Parser expression according to Migrate JWT parser expressions	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. `%{issue.cf10004.id}` or `%{issue.components.id}.` The list of available field codes and parser functions differs between JWT DC and JWT Cloud.
Clear field value	Clear field value

Write protection

Filter

Filter by project

Filter by link type

Filter by issue type

Filter by status

Filter by field value

Logical parsing mode
Parser expression according to Migrate JWT Parser expressions

The list of available field codes and parser functions differs between JWT DC and JWT Cloud.

Additional Options

Update 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

Logical parsing mode
Parser expression according to Migrate JWT parser expressions

The list of available field codes and parser functions differs between JWT DC and JWT Cloud.

Run as

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:

Selected user, where you can pick a specific user
User in field, where all User fields (e.g. Assignee or Project lead as well as all custom fields of the type User picker (single user) are listed

The default is the same as in JWT DC: Current user

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.