On this page
Introduction
The move issues post function allows you automatically to move a standard-issue type to a different project or issue type
The move issues must be the last post function of a transition.
Remark
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*
Issue type*
Fields*
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:
- Copy field from the current issue (the value from the selected field will be copied over to the new issue)
- Set field value manually (expression parser)
Issue links
You have the option to link the issue that you are currently creating to an existing issue, and you have the following options:
- is blocked by (Blocks) -inward
- blocks (Blocks) -outward
- is cloned by (Cloners) -inward
- clones (Cloners) -outward
- is duplicated by (Duplicate) -inward
- duplicates (Duplicates) -outward
- relates to (Relates) -inward
- relates to (Relates) -inward
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.
The post function will only be executed if the condition is met (returns
true
.).
Use cases and examples using this post function
Use case |
---|
No content found. |
If you still have questions, please refer to our support team.