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
| 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"
| 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
| 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
| 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)
| Please note, that in JWT Cloud, the parser expression has to return an issue key. 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)
| Please note, that in JWT Cloud, the parser expression has to return a sub-task's issue key. 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) |
| Please note, that in JWT Cloud, the parser expression has to return an issue key. The list of available field codes and parser functions differs between JWT DC and JWT Cloud. | |
Project | Current project | ||
Selected project | |||
Set project manually (parser expression) |
| Please note, that in JWT Cloud, the parser expression has to return a project ID (e.g. a field code like The list of available field codes and parser functions differs between JWT DC and JWT Cloud. | |
Summary |
| The list of available field codes differs between JWT DC and JWT Cloud. | |
Description |
| 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:
The default is the same as in JWT DC: Current user | This parameter is called Comment author in JWT Cloud. 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. |
If you still have questions, feel free to refer to our support team.