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 an 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.
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 | 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)
| 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)
| 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) |
| 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)
| 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. | |
Fields | Summary | Summary
| The list of available field codes and parser functions differs between JWT DC and JWT Cloud. |
Description | Description
| The list of available field codes and parser functions differs between JWT DC and JWT Cloud. | |
Additional Fields The expandable list below shows which JWT DC fields are available on JWT Cloud as well. | |||
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
| ||
Additional Options | Not available in JWT Cloud. | ||
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 | 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.