Migrate 'Create issue' | Decadis App Help Center

The Create issue 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 Create issue post function.
Reconfigure the post function with the help of the following list, providing the necessary basics.

Migration details

The context created.parent is not available in JWT Cloud when using parser expressions in this post function.

Mode

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

JWT DC parameter options	JWT Cloud parameter options
Single issue	Single issue
Multiple issues - Numeric	Multiple issues based on a number General parsing mode Parser expression according to Migrate JWT parser expressions
Multiple issues - JQL	Multiple issues based on an issue list General parsing mode Parser expression according to Migrate JWT parser expressions (see JQL mode in the linked page)
Multiple issues - Issue list	Multiple issues based on an issue list General parsing mode Parser expression according to Migrate JWT parser expressions
Multiple issues - Text list	Multiple issues based on a text list General parsing mode Parser expression according to Migrate JWT parser expressions

Issue type

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

JWT DC parameter options	JWT Cloud parameter options
Selected issue type	Selected issue type
Parser expression (standard issue type)	Parser expression (standard issue type) General parsing mode Parser expression according to Migrate JWT parser expressions In JWT Cloud, the parser expression has to return an issue type ID.
Parser expression (sub-task issue type)	Parser expression (sub-task issue type) General parsing mode Parser expression according to Migrate JWT parser expressions In JWT Cloud, the parser expression has to return a sub-task's issue type ID.

JWT DC parameter options

JWT Cloud parameter options

Selected issue type

Parser expression (standard issue type)

General parsing mode
Parser expression according to Migrate JWT parser expressions

In JWT Cloud, the parser expression has to return an issue type ID.

Parser expression (sub-task issue type)

General parsing mode
Parser expression according to Migrate JWT parser expressions

In JWT Cloud, the parser expression has to return a sub-task's issue type ID.

Parent

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

JWT DC parameter options	JWT Cloud parameter options
Current issue	Current issue
Parent of current issue	Parent of current issue
Set parent manually (parser expression)	General parsing mode Parser expression according to Migrate JWT parser expressions In JWT Cloud, the parser expression has to return an issue key or an issue ID

Project

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

JWT DC parameter options	JWT Cloud parameter options
Current project	Current project
Selected project	Selected project
Set project manually (parser expression)	Set project manually (parser expression) General parsing mode Parser expression according to Migrate JWT parser expressions In JWT Cloud, the parser expression has to return a project ID (e.g. a field code like `%{issue.project.id}` which returns a project id).

JWT DC parameter options

JWT Cloud parameter options

Current project

Selected project

Set project manually (parser expression)

General parsing mode
Parser expression according to Migrate JWT parser expressions

In JWT Cloud, the parser expression has to return a project ID (e.g. a field code like %{issue.project.id} which returns a project id).

Fields

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

JWT DC parameter options	JWT Cloud parameter options
Summary	Summary General parsing mode Parser expression according to Migrate JWT parser expressions
Description	Description General parsing mode Parser expression according to Migrate JWT parser expressions

JWT DC parameter options

JWT Cloud parameter options

Summary

General parsing mode
Parser expression according to Migrate JWT parser expressions

Description

General parsing mode
Parser expression according to Migrate JWT parser expressions

The list below shows which additional JWT DC fields are available on JWT Cloud as well.

JWT DC field	JWT Cloud field	Notes
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.
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)	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.

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).
Copy field value from epic issue	-
Copy field value from seed issue	Copy field value from seed 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).
Copy field value from parent of new issue	-
Set field manually (parser expression)	Set field manually (parser expression) General parsing mode Parser expression according to Migrate JWT parser expressions	In JWT Cloud 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}.`

Additionally you can copy remaining fields

Issue Links

The only difference between JWT DC and JWT Cloud is the parsing mode for the condition in the dialog for the issue link to be created. In JWT Cloud you have to

Choose the Logical parsing mode and
migrate the Parser expression according to Migrate JWT parser expressions

Additional options

Not available in JWT Cloud.

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 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: 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

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:

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