Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Panel

On this page

Table of Contents
exclude(On this page).*
stylecircle
typeflat
separatorpipe



Introduction


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


UI Text Box
typenote

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






Info
titleRemark

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*

Info
iconfalse

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)

    Expand
    titlemore info...

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


Issue type*

Info
iconfalse

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)

    Expand
    titlemore info...

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


Status*

Info

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)

    Expand
    titlemore info...

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



Fields*

Info

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

  • 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)

    Expand
    titlemore info...

    Enter plain text and optionally use field codes, e.g. %{issue.summary}, to insert field values.

    UI Text Box
    typetip

    By default, all other fields values will be retained



Additional options

Info

You have the following two options:

  •  

    Block transition and show an error message when the moving fails

  •  

    Delayed execution

    Expand
    titlemore info...

    The execution of this post function will be delayed by the value specified in milliseconds

    UI Text Box
    typetip

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



Conditional execution

Info

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

Note

The post function will only be executed if the condition is met (returns true .).



Run as

Info

Choose which user* you want to give permission to execute this post function. By default it is set to the Current user.



Warning

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 using this post function

Page properties report
firstcolumnUse case
headingsFunction, Use case description, Complexity
sortByTitle
cqllabel = "use-case" and space = currentSpace() and parent = currentContent()



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