Page History
UI Text Box | ||||
---|---|---|---|---|
| ||||
This post function automatically executes a specific transition on the selected issues or transitions issues to a selected status. It is the preferred way of executing transitions. However, in some cases, e.g. the automatic transitioning of newly created issues using the Create issue post function, users might want to use the following alternative field codes: |
Configuration
UI Expand | ||
---|---|---|
| ||
Select the issue(s) to be transitioned |
On this page
Table of Contents | ||||||||
---|---|---|---|---|---|---|---|---|
|
Introduction
The Create issue post function automatically creates a single standard-issue or sub-task in any given project. The issue type can be selected from all available issue types and sub-task issue types in the system (excluding next-gen projects).
Additional field values can be taken over or manually set using expression parser
Info | ||
---|---|---|
| ||
In this documentation and the post function configuration you will notice the symbol ( * ) next to some parameters, it means that this field is mandatory and shall not be left empty. Fields without the symbol are optional. |
Basic configuration*
Below you will find a detailed description of each parameter of the basic configuration of the function.
Mode
Info | ||
---|---|---|
| ||
Select how many issues you want to create. You can select between two options:
|
Issue type*
Info | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
The issue type of issue(s) to be created. The following options are available:
Parser expression (standard issue type)
Parser expression (sub-task issue type)
In case a sub-task is chosen, the respective parent has to selected and the following options are available: The parent issue is only shown when a sub-task is selected as issue type. Project (only for standard-issue types)* The project that the issue will be created in will come with the following options:
|
Fields*
Info |
---|
Summary* Enter a text to give a summary to your issue (like a title for the issue), and you can also use field codes. Description Enter a text to describe your issue. Additional fields Set additional field values, in the popup after clicking the Add button you can select to set the value in two ways:
|
Issue links
Info |
---|
You have the option to link the issue that you are currently creating to an existing issue, and you have the following options:
|
Conditional execution
|
UI Expand | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||
Select the transition to be executed or the status to be transitioned to. The following options are available:
|
UI Expand | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
Choose between the following options (multi choice is possible):
|
UI Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
|
UI Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
|
Enter a condition (Boolean condition) using the JWT expression parser - full feature list syntax.
You can even logically link and gather conditions in expressions as you like in order to map more complex conditions.
Note |
---|
The post function will only be executed if the condition is met (returns |
Use cases and examples
Page properties report | ||||||||
---|---|---|---|---|---|---|---|---|
|
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
Page properties | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
Page properties | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|