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

Versions Compared

Old Version 4

changes.mady.by.user Decadis AG

Saved on

compared with

New Version 5

changes.mady.by.user Decadis AG

Saved on

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.

Mode

Project*

Info
iconfalse

Select how many issues you want to create. You can select between two options:

  • Single issue
  • Multiple issues

Issue type*

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
iconfalse

The issue type of issue(s) to be created. The following options are available:

  • Selected issue type

  • Parser expression (standard issue type)

    Expand
    titlemore info...

    ((info) expects an issue type (info) the input has to be a project ID or a reference like %{issue.issueTypeproject.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 expressionParser expression (sub-task issue type)

    Expand
    titlemore info...
    (

    (info) expects

    a sub-task

    an issue type ID or

    a

    reference like %{issue.issueType.id}

    )

In case a sub-task is chosen, the respective parent has to selected and the following options are available:

  • Current issue
  • Parent issue
  • Selected issue
    • Parser expression ((info) the input has to be an issue key)

    The parent issue is only shown when a sub-task is selected as issue type.

    •  

    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

      (info) expects a status or

    Project (only for standard-issue types)*

    The project that the issue will be created in will come with the following options:

    • Current project
    • Selected project
    • Parser expression ((info) the input has to be a project ID or a

      reference like %{issue.

      project.id})
    Note
    Please note that the project selection does not show up when the issue type is a sub-task.

    • status}



    Fields*

    Info

    Summary*

    Enter a text to give a summary to your issue (like a title for the issue), and you can also use field codes.

    Description

    Enter a text to describe your issue.

    Additional fields

    Set additional field values, 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)
    Issue links


    UI Text Box
    typetip

    By default, all other fields values will be retained


    Additional options

    Info

    You have the option to link the issue that you are currently creating to an existing issue, and you have the following options:

  • is blocked by (Blocks) -inward
  • blocks (Blocks) -outward
  • is cloned by (Cloners) -inward
  • clones (Cloners) -outward
  • is duplicated by (Duplicate) -inward
  • duplicates (Duplicates) -outward
  • relates to (Relates) -inward

    • following two options:

    •  

      Block transition and show an error message when the moving fails

    •  

      Delayed execution

      Expand

      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)

    relates to (Relates) -inward



    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.



    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.