Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT remote actions

Cloud migration hub

Additional product info

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »

On this page

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

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

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*

Select the issue type to be created. The following options are available:

  • Selected issue type

  • Parser expression (standard issue type)

    Expects an issue type ID or reference like %{issue.issueType.id}

  • Parser expression (sub-task issue type)

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

Parent issue (only for sub-tasks)*

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

  • Current issue
  • Parent issue
  • Selected issue

  • Parser expression

    The input has to be an issue key

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

Project (only for standard issue types)

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

  • Current project
  • Selected project

  • Parser expression

    The input has to be a project ID or a reference like %{issue.project.id}

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

Summary*

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

Description

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

Additional fields

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

    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"

    Error rendering macro 'multimedia'

    com.atlassian.renderer.v2.macro.MacroException: Cannot find attachment 'affects-versions-id.mp4'

  • Set field value manually (parser expression) - Read more about parser expressions.
  • The third option Selected value is available for the following fields:
    • Jira Software fields
    • User related fields (Assignee, Reporter)
    • Version related fields (Affects version/s, 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 radiobutton value, for example, can be set like this:


Run as

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

Conditional execution

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.

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

Use cases and examples

Use case
No content found.

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