Page History
UI Text Box | ||||
---|---|---|---|---|
| ||||
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
|
| |||||||||||
Multiple issues - JQL | Select "Multiple issues based on an issue list"
|
| |||||||||||
Multiple issues - Issue list | Multiple issues based on an issue list
|
| |||||||||||
Multiple issues - Text list | Multiple issues based on a text list
|
| |||||||||||
Issue type | Selected issue type | Selected issue type | |||||||||||
Parser expression (standard issue type) | Parser expression (standard issue type)
|
| |||||||||||
Parser expression (sub-task issue type) | Parser expression (sub-task issue type)
|
| |||||||||||
Parent | Current issue | Current issue | |||||||||||
Parent of current issue | Paret of current issue | ||||||||||||
Set parent manually (parser expression) |
|
| |||||||||||
Project | Current project | ||||||||||||
Selected project | |||||||||||||
Set project manually (parser expression) |
|
| |||||||||||
Summary |
|
| |||||||||||
Description |
|
| |||||||||||
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 |
|
Post function parameters | Notes | |
---|---|---|
Server / DC | Cloud | |
Mode | Mode | Mode selector:
|
| ||
Issue Type | Issue 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. |
Project | Project | 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. |
Summary | Summary | 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. |
Description | Description | |
Additional fields | Fields | |
Issue links | Issue links | |
Additional Options | In Jira Cloud, there are no Temporary fields, so there are no additional options. | |
Conditional execution | Conditional execution | |
Run as | Run as | In the Cloud, there are available only user fields. |
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|