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 2

changes.mady.by.user Decadis AG

Saved on

compared with

New Version 3

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

Basic configuration*

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

Mode


Target issue*

Info
iconfalse

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

  • Single issue
  • Multiple issues
Issue type

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*

Parser expression (sub-task issue type)

Info
iconfalse

The issue type of issue(s) to be createdSelect the transition to be executed or the status to be transitioned to. The following options are available:

  • Selected issue type
  • Parser expression (standard issue type)Execute transition
Expand
titlemore info...

Pick either a transition which is shown by name and ordered by workflows or a parser expression ((info) expects a transition ID)

  • Transition to status

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

Expand
titlemore info...

Pick either a status which is shown by name or a parser expression ((info)

expects a sub-task 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.

    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})
    NotePlease note that the project selection does not show up when the issue type is a sub-task

    •  expects a status ID). If more than one transition is available to reach the configured status, the first found transition 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

    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

    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.