Versions Compared

Key

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


UI Text Box
sizemedium
typeinfo

This post function automatically executes a specific transition on the selected issues or transitions issues to a selected status

It is the preferred way of executing transitions. However, in some cases, e.g. the automatic transitioning of newly created issues using the Create issue post function, users might want to use the following alternative field codes:


Image AddedConfiguration

UI Expand
titleTarget issue

Select the issue(s) to be transitioned. The following options are available:

OptionDescription
Current issueThe current issue will be transitioned.
Parent issueThe current issue's parent will be transitioned.
Sub-tasksThe current issue's sub-tasks will be transitioned. If you choose this option you can further filter your selection (e.g. by issue type or status). Only useful for standard issues
Sibling sub-tasksThe current issue's sibling sub-tasks will be transitioned. Only useful if the current issue is a sub-task
Linked issuesLinked issues will be transitioned. If you choose this option you can further filter your selection (e.g. by issue type or status). 
Linked epicThe related epic will be transitioned.
Issues under epicAll issues related to the same epic will be transitioned. If you choose this option you can further filter your selection (e.g. by issue type or status). 
Sibling issues under epicAll sibling issues related to the same epic will be transitioned. If you choose this option you can further filter your selection (e.g. by issue type or status). 
Panel

On this page

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

Introduction

Image Removed

The Create issue post function automatically creates a single standard-issue or sub-task in any given project. The issue type can be selected from all available issue types and sub-task issue types in the system (excluding next-gen projects).

Additional field values can be taken over or manually set using expression parser

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.

Image RemovedBasic configuration*

Below you will find a detailed description of each parameter of the basic configuration of the function.

Target issue*

Info
iconfalse

Select the issue to be transitioned, the following options are available:

  • Current issue
  • Parent issue
  • Sub-tasks
  • Sibling sub-tasks
  • Linked issues
  • Linked epic
  • Issues under epic
  • Sibling issues under epic
    Set target issue manually (parser expression)
    Expand
    titlemore info...

    (info) the input has to be an issue key

    Mode*

    Define the issues that will be transitioned by defining an expression. The JQL mode and Issue list mode are available.

    UI Text Box
    typenote

    The expression must return either a valid JQL expression or an issue list with issue keys.




    Pick either a status which is shown by name or a parser expression ((info) expects a status ID).
    UI Expand
    titleMode
    Info
    iconfalse

    Select the transition to be executed or the status to be transitioned to. The following options are available:

    OptionDescription
    Execute transition

    Either select an existing transition from any available workflow or set the transition

    Expand
    titlemore info...

    Pick either a status which is shown by name or a parser expression ((info) expects a status ID). If more than one transition is available to reach the configured status, the first found transition will be executed.

    Transition to status

    Expand
    titlemore info...

    manually using a parser expression in Basic text mode.

    UI Text Box
    typeinfo

    The expression must return a transition name.


    Transition to status

    Either select an existing status from any available workflow or set the status manually using a parser expression in Basic text mode.

    UI Text Box
    typeinfo

    The expression must return a status name.

    If more than one transition is available to reach the configured status, the first transition (found

    transition

    by Jira) will be executed.

    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, 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)
    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
    • relates to (Relates) -inward

    Conditional execution



    UI Text Box
    typetip

    Both, transition or target status, have to be available from the issues' current status. The provided list, however, contains all statuses and transitions in the system.



    UI Expand
    iconfalse
    titleAdditional options

    Choose between the following options (multi choice is possible):

    OptionDescription
    Ignore conditions

    Existing conditions in the transitions to be executed will be ignored.

    Ignore validators

    Existing validators in the transitions to be executed will be ignored.

    Ignore project permissions

    The "Transition Issues" project permission will be ignored for the user running this post function.
    Delayed execution

    Include Page
    DECADIS:_snip_delayed_execution
    DECADIS:_snip_delayed_execution



    UI Expand
    iconfalse
    titleConditional execution

    Include Page
    DECADIS:_snip_condExecution_Server
    DECADIS:_snip_condExecution_Server


    UI Expand
    iconfalse
    titleRun as

    Include Page
    DECADIS:_snip_runAs_Server_postFunction
    DECADIS:_snip_runAs_Server_postFunction



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

    Use cases and examples using this post function

    Image AddedUse cases and examples


    Page properties report
    firstcolumnUse case
    headingsFunction, Use case description, ComplexityJWT feature, Workflow function, Parser functions, Label
    sortByTitle
    cqllabel = "use-case-workflow" and space = currentSpace() and parent ancestor = currentContent()
    If you still have questions, please refer to our support team.


    Excerpt Include
    DECADIS:Contact support
    DECADIS:Contact support
    nopaneltrue


    Page properties
    hiddentrue


    Tech review

    Status
    colourGreen
    titledone

    Style guide

    Status
    colourGreen
    titledone

    Status
    titletodo
    Status
    colourYellow
    titleReady for review
    Status
    colourGreen
    titledone
    Status
    colourRed
    titleflagged


    Page properties
    hiddentrue


    Short descriptionTransition any issue to any available target status.
    Label

    Status
    colourRed
    titlestaff pick