Skip to main content
assistive.skiplink.to.breadcrumbs
assistive.skiplink.to.header.menu
assistive.skiplink.to.action.menu
assistive.skiplink.to.quick.search

Search

Jira Workflow Toolbox Cloud

Use case library

JWT expression editor

JWT expression parser functions

JWT remote actions

Cloud migration hub

Additional product info

Skip to end of banner Go to start of banner

Migrate 'Create issue'

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

The post function 'Create issue' is available in both JWT DC and JWT Cloud. There are slight differences in the parameters and their options. The table below shows the mapping of the individual parameters and options from JWT DC to JWT Cloud.

Please note that the context created.parent is not available in JWT Cloudwhen using parser expression in this post function.

JWT DC parameter

JWT DC parameter options

JWT Cloud parameter options

Notes

Mode

Single issue

Single issue

Multiple issues - Numeric

Multiple issues based on a number

General 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.

Multiple issues - JQL

Select "Multiple issues based on an issue list"

General parsing mode
Parser expression according to Migrate JWT Parser expressions (see JQL mode in Migrate JWT Parser expressions)

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

Multiple issues - Issue list

Multiple issues based on an issue list

General 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.

Multiple issues - Text list

Multiple issues based on a text list

General 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.

Issue type

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

Please note, that in JWT Cloud, the parser expression has to return an issue type ID.

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

Parser expression (sub-task issue type)

Parser expression (sub-task issue type)

General parsing mode
Parser expression according to Migrate JWT Parser expressions

Please note, that in JWT Cloud, the parser expression has to return a sub-task's issue type ID.

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

Parent Current issue Current issue

Parent of current issue Paret of current issue

Set parent manually (parser expression)

General parsing mode
Parser expression according to Migrate JWT Parser expressions

Please note, that in JWT Cloud, the parser expression has to return an issue key or an issue ID

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

Project 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

Please note, that 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).

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

Fields

Summary

Summary

General 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.

Description

Description

General parsing mode
Parser expression according to Migrate JWT Parser expressions

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

Additional Fields

Additional 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
Summary	Summary
Description	Description
Affected versions	Affects version/s	This fields requires a list of IDs of the values to be set.
Assignee	Assignee	An Atlassian account ID is expected.
Checkboxes (Custom field)	Checkboxes	This fields requires the ID of the value to be set.
Components	Component/s	This fields 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 fields requires a list of IDs of the values to be set.
Group picker (Multiple groups) (Custom field)	Group Picker (multiple groups)
Group picker Single group) (Custom field)	Group Picker (single group)
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 fields requires the ID of the value to be set.
Radio buttons (Custom field)	Radio Buttons	This fields 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 fields requires the ID of the value to be set.
Select list (cascading) (Custom field)	Select list (cascading)	This fields requires the IDs of the values to be set, e.g.
Select list (multiple choices) (Custom field)	Select List (multiple choices)	This fields requires a list of IDs of the values to be set.
Select list (single choice) (Custom field)	Select List (single choice)	This fields requires the ID of the value to be set.
Sprint (Custom field)	Sprint	This fields 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 fields requires a list of IDs of the values to be set.
Version picker (single version) (Custom field)	Version Picker (single version)	This fields 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 chosing the option "Copy field value from...") or
writing a parser expression which returns the ID of the value which shall be set when chosing 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.

JWT DC option	JWT Cloud option	Notes
Automatic	-	Please note, that this option is 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	Please note, that 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}.`

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 -

Conditional execution

Logical parsing mode
Parser expression according to Migrate JWT Parser expressions

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.

If you still have questions, feel free to refer to our support team.

Powered by Atlassian Confluence 8.5.7, themed by Refined 7.5.3 and Decadis AG