On this pageIntroductionThe move issues post function allows you automatically to move a standard-issue type to a different project or issue type
|
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. |
Below you will find a detailed description of each parameter of the basic configuration of the function.
Select the project which the issue will be moved to and you have the following options:
|
Select the issue type which the issue will be moved to and you have the following options:
|
Select the status which the issue will be moved to and you have the following options:
|
Define further fields to be updated, in the popup after clicking the Add button you can select to set the value in two ways:
|
You have the following two options:
|
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.
|
Choose which user* you want to give permission to execute this post function. By default it is set to the Current user. |
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 the valid configurations (issue type and workflow statuses) for all sub-tasks issues exist in the target project. |
Use cases and examples using this post function
If you still have questions, please refer to our support team.