The move issues post function allows you to automatically move a standard-issue type to a different project or issue type.

The move issues must be the last post function of a transition.

Select the project which the issue will be moved to by selecting one of the following options:

• Retain the project
• Selected project

• Set project manually (advanced text expression)

  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
• Selected issue type

• Set issue type manually (advanced text expression)

  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
• Selected status

• Set status manually (advanced text expression)

  The expression must return a status name or reference like %{issue.status}

  
  

Define further fields to be updated.

In the opening popup you can select how the field should be set:

• 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)
  Enter plain text and optionally use Field codes, e.g. %{issue.summary}, to insert field values.

  By default, all other field values will be retained.

  
  

You have the following two options:

1. Block transition and show an error message when the move operation fails
   

2. Delayed execution (The execution of this post function will be delayed by the value specified in milliseconds)

   The maximum delay is 60,000 milliseconds (60 seconds)

   
   

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.