You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

On this page

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.


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.

Project*

Select the project which the issue will be moved to and you have the following options:

  • Retain the project
  • Selected project
  • Set project manually (parser expression)

    (info) the input has to be a project ID or a reference like %{issue.project.id}

Issue type*

Select the issue type which the issue will be moved to and you have the following options:

  • Retain the issue type
  • Selected issue type
  • Set issue type manually (parser expression)

    (info) expects an issue type ID or reference like %{issue.issueType.id} 

Status*

Select the status which the issue will be moved to and you have the following options:

  • Retain the status
  • Selected status
  • Set status manually (parser expression)

    (info) expects a status or reference like %{issue.status}

Fields*

Define further fields to be updated, in the popup after clicking the Add button you can select to set the value in two ways:

  1. Copy field from the current issue (the value from the selected field will be copied over to the new issue)
  2. 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 fields values will be retained

Additional options

Additional options

You have the following two options:

  1. Block transition and show an error message when the moving 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)

Conditional execution

Enter a condition (Logical / 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 .).

Run as

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



If you still have questions, feel free to refer to our support team.