Page History
UI Text Box | ||||
---|---|---|---|---|
| ||||
The post function 'Create issue' function Update or copy field values of JWT DC is available in both JWT DC and JWT Cloud as Update fields. There 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. | ||||
UI Text Box | ||||
| ||||
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 |
---|
Target issue |
Current issue |
Current issue |
Multiple issues based on a number
- General parsing mode
- Parser expression according to Migrate JWT Parser expressions
UI Text Box | ||
---|---|---|
| ||
The list of available field codes and parser functions differs between JWT DC and JWT Cloud. |
Select "Multiple issues based on an issue list"
Parent issue | Parent issue | |
Sub-tasks | Select option Parser expression
|
|
The list of available field codes and parser functions differs between JWT DC and JWT Cloud.
Multiple issues based on an issue list
- General parsing mode
- Parser expression according to Migrate JWT Parser expressions
| |||||
Sibling sub-tasks |
|
|
|
Linked issues |
Select option Parser expression |
|
|
|
The list of available field codes and parser functions differs between JWT DC and JWT Cloud.
Selected issue type
Parser expression (standard issue type)
| |
Linked epic | Select option Parser expression
|
|
|
UI Text Box | ||
---|---|---|
| ||
The list of available field codes and parser functions differs between JWT DC and JWT Cloud. |
Parser expression (sub-task issue type)
| |
Issues under epic | Select option Parser expression
|
|
|
| |
Sibling issues under epic | Select option Parser expression
|
UI Text Box | ||
---|---|---|
| ||
The list of available field codes and parser functions differs between JWT DC and JWT Cloud. |
|
|
| |
Set target issues |
UI Text Box | ||
---|---|---|
| ||
The list of available field codes and parser functions differs between JWT DC and JWT Cloud. |
manually (parser expression) |
Parser expression |
UI Text Box | ||
---|---|---|
| ||
The list of available field codes and parser functions differs between JWT DC and JWT Cloud. |
Fields
Summary
- General parsing mode
- Parser expression according to Migrate JWT Parser expressions
UI Text Box | ||
---|---|---|
| ||
The list of available field codes and parser functions differs between JWT DC and JWT Cloud. |
Description
- General parsing mode
- Parser expression according to Migrate JWT Parser expressions
UI Text Box | ||
---|---|---|
| ||
The list of available field codes and parser functions differ between JWT DC and JWT Cloud. |
|
|
%{issue.project.id}
which returns a project id).
|
Fields | |||||
|
|
Copy field value from seed issue
Copy field value from seed issue
type | info |
---|
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).
|
| ||||||||
Write protection |
- |
Additional Options |
|
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
| |||
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 |
|
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|