Page History
UI Text Box | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This | ||||||||||
Panel | ||||||||||
On this page
IntroductionThe move issues post function allows you automatically to move a standard- issue type to a different project to other projects, statuses or issue typetypes. |
UI Text Box | ||
---|---|---|
| ||
The move issues This post function must be the last post function of a transition. |
Configuration
UI Expandinfo | ||
---|---|---|
| ||
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*
icon | false |
---|
The issue type of issue(s) to be created. The following options are available:
Parser expression (standard issue type)
Expand | ||
---|---|---|
| ||
( expects an issue type ID or reference like |
Parser expression (sub-task issue type)
Expand | ||
---|---|---|
| ||
|
| |||||||||||||
Select the project which the issue will be moved to by selecting one of the following options:
|
UI Expand | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||
Select the issue type which the issue will be moved to by selecting one of the following options:
|
UI Expand | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||
Select the status which the issue will be moved to by selecting one of the following options:
|
UI Expand | |||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||
Optionally define fields and target values that should be updated as part of the move operation. Upon selecting a field that should be updated from the dropdown you will be presented with these options:
Write protection
|
UI Expand | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
You have the following two options:
|
UI Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
|
UI Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
|
UI Text Box | ||
---|---|---|
| ||
In case the configuration is incorrect, e.g. the issue type is not available in the target project or the target status is not available for the new issue type, the post function will be skipped. After the execution of the post function you might need to refresh your browser in order to view the the issue fully updated to the new project and issue type. |
UI Text Box | ||
---|---|---|
| ||
Moving individual sub-tasks is currently not supported. Sub-tasks can only be moved in sync with their parent issue. When moving a parent issue, make sure that valid configurations (issue type and workflow statuses) for all sub-tasks issues exist in the target project. |
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:
- Current project
- Selected project
- Parser expression ( the input has to be a project ID or a reference like
%{issue.project.id})
Note |
---|
Please note that the project selection does not show up when the issue type is a sub-task. |
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
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 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|