Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT remote actions

Cloud migration hub

Additional product info

Versions Compared

Old Version 10

changes.mady.by.user Ute Masermann

Saved on

compared with

New Version 11

changes.mady.by.user Ute Masermann

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


UI Text Box
sizemedium
typeinfo

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



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


UI Text Box
typeinfo

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"


UI Text Box
typeinfo

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


UI Text Box
typeinfo

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


UI Text Box
typeinfo

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)


UI Text Box
typeinfo

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


UI Text Box
typeinfo

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)


UI Text Box
typeinfo

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


UI Text Box
typeinfo

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


ParentCurrent issueCurrent issue
Parent of current issueParet of current issue 
Set parent manually (parser expression)


UI Text Box
typeinfo

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


UI Text Box
typeinfo

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


ProjectCurrent project

Selected project

Set project manually (parser expression)


UI Text Box
typeinfo

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


UI Text Box
typeinfo

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


Summary
  • General parsing mode
  • Insert parser expression replacing JWT DC field codes with JWT Cloud field codes according to Migrate field codes


UI Text Box
typeinfo

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


Description


UI Text Box
typeinfo

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


Additional Fields


Issue Links


Additional Options
-
Conditional execution

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



UI Text Box
typeinfo

This parameter is called Comment author in JWT Cloud.


UI Text Box
typeinfo

Since only those fields can be selected which hold a user it may happen that the value from JWT DC cannot be mapped to the respective field in JWT Cloud.

Post function parameters

Notes

Image Removed

Server / DC

Image Removed

Cloud

Image Removed

ModeMode

Mode selector:

  • Server: Two options, we have "Single" and "Multiple". If the second one is chosen, then the Expression field is visible and the user can write there a JQL expression, issue list expression, text list expression, or numeric expression.
  • Cloud: We have several options: single issue, Multiple by text list, Multiple by number, and Multiple by issue list (General parser and Jira Expression).
Issue TypeIssue Type

We have the same options in both of them, but in the Cloud version, we have the option to implement the parser expression in General parser and in Jira Expression.

ProjectProject

We have the same options, but in the Cloud version, we also have Seed issue's project, which is useful when we have selected Multiple by issue list.

SummarySummary

There are some differences in some of the fields, for example, in the Assignee field in the Cloud version we don't have the Automatic option, but the rest of the options are available.

DescriptionDescriptionAdditional fieldsFieldsIssue linksIssue linksAdditional OptionsIn Jira Cloud, there are no Temporary fields, so there are no additional options.Conditional executionConditional executionRun asRun asIn the Cloud, there are available only user fields.



Excerpt Include
DECADIS:Contact support
DECADIS:Contact support
nopaneltrue