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.

Configuration

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.

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.

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.

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

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

Set or clear values for specific fields.

In the popup after clicking the Add button you can select to set the value in three - or when dealing with selectable fields - four ways:

  • Copy field from current issue
  • The fourth 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:

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

Use cases and examples