Page History
| Section | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Purpose
| Status | ||||
|---|---|---|---|---|
|
The Move issues post function allows you to move a standard issue type to a different project or issue type. Both the target issue type and workflow status must be available in the target project.
The post function must be the last post function of a transition.
The following options are available:
- Project (Select the target project)
- Issue type (Select the target issue type)
- Status (Select the target status)
- Set fields (Select additional fields to be set)
- Additional actions (
- It is possible to show a meaningful error message and stop the execution of the entire transition should the post function fail.
Status colour Yellow title since version 2.6.0
- It is possible to
- execute the post function with a custom delay after current transition has finished.
Status colour Yellow title since version 2.7.0
- It is possible to show a meaningful error message and stop the execution of the entire transition should the post function fail.
- Conditional execution (Optional boolean expression that should be satisfied in order to actually execute the post function)
- Run as (Select the user that will be used to execute the post function)
| Warning |
|---|
Moving individual sub-tasks is currently not supported. Sub-tasks can only be moved in sync with their their parent issue. When moving a parent issue make sure that the valid configurations (issue type and workflow statuses) for all sub-taks issues exist in the target project. |
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. Optionally you can decide whether you want to display an error and abort the execution of the entire transition.
Example: Moving current issue to project Development and converting it into Task issue type
In this example we show how to configure the Move issues post function for moving the current issue to the project Development, and at the same time converting it from any issue type into a Task.
We are conditioning the execution of the post function to the presence of any of the following components in the issue: "Budget", "Payment" or "Cash". To execute the post function unconditionally, the field Conditional execution should remain empty.
We are also adding the string "(moved from project <original_project_key>)" to the summary of the moved issue, and leaving the following comment: "The issue was moved from project <original_project_key> by <user_who_executes_the_post-function> on <date_time_of_issue_moving>."
Once configured, the Move issues post function will look like this:
Note that the post function has to be moved to the last position of the post function sequence. Otherwise nothing will happen.
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.
