Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT remote actions

Cloud migration hub

Additional product info

Versions Compared

Old Version 16

changes.mady.by.user Iheb Kharab

Saved on

compared with

New Version Current

changes.mady.by.user Iheb Kharab

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

UI Text Box
sizemedium
typeinfo

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 issues issue types and sub-task issue types in the system (excluding next-gen projects).

Additional field values can be inherited or manually set using parser expressions.


Image AddedConfiguration

ui-text-box
typenote

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.

Add parameters to the function

Below you will find a detailed description of each parameter to be added to the function.

Issue type*

Expand
titleMode

The mode parameter defines how many issues you want to create. You can either choose to create just one single issue or multiple ones.

The following modes are available:

OptionDescription
Single issue

If you select this mode, you will be dynamically guided to ultimately specify what issue type will be created and where it will be created. This may include a multi-layered selection process.

In this mode, only one single issue will be created.

Multiple issues based on a text list
Determining the number of issues is done using a parser expression. This parser expression has to return a text list. The number of list elements defines the number of issues to be created.

You can access the respective value using %{seed.text} within all subsequent parameters (except "Conditional execution").  Learn more about seeds.

Multiple issues based on a number
Determining the number of issues is done using a parser expression. This parser expression has to return a number. This number defines the number of issues to be created.

You can access the current value using %{seed.number} within all subsequent parameters (except "Conditional execution"). Learn more about seeds.

Multiple issues based on an issue list
Determining the number of issues is done using a parser expression. This parser expression has to return an issue list. This number of list elements defines the number of issues to be created.

You can ccess the current value using %{seed.issue.somefield} or %{seed.parent.somefield} within all subsequent parameters (except "Conditional execution"). Learn more about seeds.

Include Page
DECADIS:_snip_tryExpression_Cloud
DECADIS:_snip_tryExpression_Cloud


more info...

:

UI Expand
titleIssue type
Info
iconfalse

Select the issue type to be created.

The following options are available:

  • Selected issue type

  • Parser expression (standard issue type)

Expand
title
UI Text Box
typeinfo

Expects an issue type ID or

reference

a field code like %{issue.issueType.id}


  • Parser expression (sub-task issue type)

    :

    Expand
    titlemore info...
    UI Text Box
    typeinfo

    Expects a sub-task issue type ID or

    a reference

    a field code like %{issue.issueType.id}



    • UI Text Box
    typenote

    In case a sub-task is chosen, the respective parent has to be selected.



    UI Expand
    titleParent issue (only for sub-tasks)
    *more info...


    Info
    iconfalse

    Choose the parent issue under which you want to create a of the sub-task to be created. The following options are available:

    • Current issue
    • Parent issue
    • Selected issue

      Parser expression

    • Seed issue's parent (only available if mode "Multiple issues based on an issue list" was selected)

    • Parser expression:

    Expand
    title
    UI Text Box
    typeinfo

    The input has to be an issue key



    UI Text Box
    typenote

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



    UI Expand
    titleProject (only for standard issue types)
    more info...

    Info
    iconfalse

    The project the issue will be created in. It comes with the following options:

    • Current project
    • Selected project
    • Seed issue's project (only available if mode "Multiple issues based on an issue list" was selected)

    • Parser expression:

      Parser expression

    Expand
    title
    UI Text Box
    typeinfo

    The input has to be a project ID

    or a reference

    or a field code like %{issue.project.id}


    UI Text Box
    typeinfo

    Please note that the project selection does not show up when the issue type is a sub-task issue type is selected.

    Summary*



    UI Expand
    titleSummary
    Info
    iconfalse

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

    Description

    or functions provided by the selected parsing mode.


    UI Expand
    titleDescription
    Info
    iconfalse

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

    UI Text Box
    typetip

    Test your expressions by clicking  Image Removed on the top right of the expression box. Learn more about Parser expression editor.

    Additional fields

    description} or functions provided by the selected parsing mode. You can enrich the styling of your description by using the available markdowns.


    UI Expand
    iconfalse
    titleAdditional fields

    In addition to the summary and description of an issue, any other field supported by JWT for Jira Cloud can be set when creating the issue.

    After selecting a field and clicking the Add button, you can select in the popup how to set the value. There are three or - when dealing with selectable fields - four options

    Info
    iconfalse
    typetip

    Optionally set additional field values.

    In the popup after clicking the Add button you can select to set the value in various ways:

    • Copy field from current issue
    Excerpt
    Expand
    titlemore info..
    UI Text Box
    typeinfo

    The value from the selected field will be copied over to the new issue.

    When copying a null/none value to a custom field which has defined default values, the default values will be set.
    No check will be done when trying to copy a null value to a field which cannot be set to null (e.g. Resolution).

    For certain fields you need to copy over the field value ID instead of the actual text value. If you use the field dropdown, the respective field code will be pre-populated and has a format of "Field name ID"

    Multimedia
    nameaffects-versions-id.mp4
    width700px

  • Set field value manually (parser expression) - Read more about parser expressions.
    • The third
  • Copy field from seed issue (only available if mode "Multiple issues based on an issue list" was selected)
  • Set field value manually - Read more about the JWT expression editor
  • The option Selected value is available for the following fields types:
    • Jira Software related fields like Sprint or Epic
    • User related fields
    (
    • like Assignee
    ,
    • or Reporter
    )
    • Version related fields
    (Affects version/s,
    • like Affects- or Fix version/s
    )
    • Component/s
    • Labels
    • Priority
    • Resolution
    • Security level
    • and all option based custom fields that are supported

  • For every selectable field type you can select one of the predefined options for this field that are available in the global context .

    Simply use the UI elements you are used to when creating or editing an issue. A checkbox value, for example, can be set like this:

    Image Removed

    • UI Expand
    titleRun as

    Choose which user* will be able to execute the post function. By default, it is set to the Current user.

    Conditional execution


    UI Expand
    titleIssue links

    Optionally define issue links to be created for the new issue(s). You have the option to link the issue that you are currently creating to various other issues. 

    Include Page
    DECADIS:_snip_available_options
    DECADIS:_snip_available_options

    OptionDescription
    Current issueLink the issue to be created to the current issue.
    Parent of current issueLink the issue to be created to the parent of the current issue.
    Parent of new issueLink the issue to be created to the parent of the sub-task to be created. Only available if the issue to be created is a sub-task.
    Epic of current issueLink the issue to be created to the related Epic of the current issue.
    Seed issueLink the issue(s) to be created to a seed issue. Only available if mode "Multiple issues based on an issue list" was selected.
    Select issues manually (parser expression)

    Link the issue to be created to the issues returned by the parser expression (General mode or Jira expression mode)

    Condition

    You can optionally specify a logical expression or a Jira expression depending on the chosen Parsing mode to define the circumstances (or conditions) under which the link should be created.


    UI Expand
    titleRun as

    Include Page
    DECADIS:_snip_runAs_Cloud
    DECADIS:_snip_runAs_Cloud

    ui-
    Info
    iconfalse

    Enter a condition (a logical expression) using the expression parser syntax.

    You can even logically link and gather conditions in expressions as you like in order to map more complex conditions.

    ui-text-box
    typenote

    The post function will only be executed if the condition is met (returns true ).configured user must have all necessary permissions to transition the target issue.



    UI Expand
    titleConditional execution

    Include Page
    DECADIS:_snip_condExecution_Cloud
    DECADIS:_snip_condExecution_Cloud



    Use cases and examples

    Page properties report
    firstcolumnUse case
    headingsFunctionJWT feature, Workflow function, Parser functions, Use case description, Complexity
    sortByTitle
    cqllabel = "use-case" and space = currentSpace() and ancestor = "2254571838569502"

    Excerpt Include
    DECADIS:Contact support
    DECADIS:Contact support
    nopaneltrue