Page History
UI Text Box | ||||
---|---|---|---|---|
|
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
On this page
|
Introduction
The Transition issue post function automatically |
Additional field values can be inherited or manually set using parser expressions.
The configuration
borderColor | #006275 |
---|
The table below lists all available parameters that have to (*) or optionally can be set in this post function.
The issue type of the issue to be created. The following options are available:
- Selected issue type
- Parser expression (standard issue type) ( expects an issue type ID or reference like
%{issue.issueType}
) - Parser expression (sub-task issue type) ( expects an sub-task issue type ID or a reference like
%{issue.issueType}
)
In case a sub-task is chosen, the respective parent has to selected.
executes a specific transition on one ore multiple issues or transitions the issues to the selected status. Both, transition and target status, have to be available from the issue's current status. |
Configuration
UI Expand | ||
---|---|---|
| ||
The issues to be transitioned. If a list of issue keys is passed, the transition will be performed for every issue in the list. |
The following options are available:
|
The parent issue is only shown when a sub-task is selected as issue type.
The project the issue will be created in. It comes with the following options:
- Current project
- Selected project
- Parser expression ( the output has to be a project ID or a reference like %{issue.project.id})
Please note that the project selection does not show up when the issue type is a sub-task.
%{issue.summary}
, to insert field values.%{issue.summary}
, to insert field values.Optionally set additional field values.
In the popup after clicking the Add button you can select to set the value in two ways:
- Copy field from current issue (the value from the selected field will be copied over to the new issue)
- Set field value manually (parser expression)
Select the user that will be used to execute this post function (the issue creator). It can be chosen from one of the following options:
- Current user
- Selected user
- Assignee
- Reporter
- Creator
- Project lead
- Parent's assignee
- Parent's reporter
- Parent's creator
|
UI Expand | |
---|---|
|
Enter a condition (a logical expression) using the expression parser syntax.
You can even logically link and nest conditions in expressions as you like in order to map more complex conditions.
The post function will only be executed if the condition is met (returns true
.).
Purpose
This post function executes a specific transition on the selected issue or transition the issue to a selected status. Both, transition and target status, have to be available from the issue's current status.
Configuration
Target issue
The issue to be transitioned. The following options are available:
| |||||
Select the transition to be executed or the status to be transitioned to. You can choose between to options:
|
|
|
|
|
|
UI Expand | ||
---|---|---|
| ||
Executing the post function will be delayed by the specified value in milliseconds. Please note that you are not able to define a value that is greater than 120 seconds. |
UI Expand | ||
---|---|---|
|
Select the user that will be used to execute this post function. It can be chosen from one of the following options:
- Current user
- Selected user
- Assignee
- Reporter
- Creator
- Project lead
- Parent's assignee
- Parent's reporter
- Parent's creator
|
UI Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
|
Use cases and examples
Page properties report | ||||||||
---|---|---|---|---|---|---|---|---|
|
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
Enter a condition using the expression parser syntax. You can even logically link and nest conditions in expressions as you like in order to map more complex conditions.
The post function will only be executed if the condition is met.
Related use cases
Status | ||||
---|---|---|---|---|
|