This post function allows you to move a standard issue type to other projects, statuses or issue types.
Select the project which the issue will be moved to by selecting one of the following options:
|Retain the project||The project will not be updated. This option makes sense, if you want to move an issue to an issue to other projects, statuses or issue types.|
|Selected project||Select the target project from the list of available projects.|
|Set project manually (parser expression)|
Specify the target project by an expression using the Advanced text mode.
The expression must return a project key or project name.
Select the issue type which the issue will be moved to by selecting one of the following options:
Retain the issue type
|The issue type will not be updated.|
Selected issue type
|Select the target issue type from the list of available issue types.|
|Set issue type manually (parser expression)|
Specify the target issue type by an expression using the Advanced text mode.
The expression must return an issue type name.
Select the status which the issue will be moved to by selecting one of the following options:
Retain the status
|The status will not be updated.|
|Select the target status from the list of available statuses.|
|Set status manually (parser expression)|
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:
|Automatic||This option is only available for the field Assignee.|
|Selected value||Select a specific value from the dropdown list.|
|Copy field value from current issue||Copy the value from a field in the current issue. Select the field you want to copy the value from.|
|Copy field value from parent of new issue||This option is only available if you create a sub-task under a new parent. Only available if the issue to be created is a sub-task.|
|Set field value manually (parser expression)|
Select the field to copy from using an expression.
Learn more about the possibilities of the JWT expression editor.
|Clear field value||Clear the field value.|
By default, all other field values will be retained.
You have the following two options:
Block transition and show an error message when the move operation fails
|In case the move operation fails, e.g. because the specified issue type is not available in the target project, the entire transition will be aborted and an error message is shown to the user.|
The execution of this post function will be delayed by the value specified in milliseconds.
This parameter is useful, when multiple operations have to be performed in a single transition. The delayed execution ensures that all previous operations have been completed, e.g. field values that are referenced in this post function are present.
The maximum delay is 60,000 milliseconds (60 seconds).
The result of the logical expression must return a boolean value of either:
true→ the post function will be executed
false→ the post function will not be executed
Using the conditional operator, even complex or multi-layered conditions can be constructed.
Make sure to learn more about defining logical expressions and browse through the various examples here: Logical mode
Make sure that the user running the post function has all the relevant permissions to perform the actions defined in the configuration (e.g. "Update Issues")!
If you want to keep track the actions being performed automatically, we suggest to create a dedicated JWT account, granted all relevant permissions, and use it in the Run as parameter to identify which changes have been made with JWT.
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.
This post function must the last post function of a transition.
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.