Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT workflow functions

JWT remote actions

JWT automation rules

JWT calculated fields

JWT calendars

JWT properties

JWT JQL functions

Cloud migration hub

Additional product info

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

Compare with Current View Page History

« Previous Version 28 Next »

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.

Configuration

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)

    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)

    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)

    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)

    1. 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

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

You can optionally specify a logical expression to define the circumstances (or conditions) under which the post function should be executed.

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

Run as

Choose which user* will be able 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

Use case
No content found.

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