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 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 a field code like %{issue.issueType.id}

  • Parser expression (sub-task issue type):

    Expects a sub-task issue type ID or a field code like %{issue.issueType.id}


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

Choose the parent issue of the sab task to be created. 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 issue type is selected.

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 field code like %{issue.project.id}

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

Enter plain text and optionally use field codes, e.g. %{issue.summary} or functions provided by the selected parsing mode.

Enter plain text and optionally use field codes, e.g. %{issue.description} or functions provided by the selected parsing mode. You can enrich the styling of your description by using the avaible markdowns.

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 to set the value in two- or when dealing with selectable fields - three ways:

  • Copy field from current issue
  • 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 like Affects- or Fix version/s
    • Component/s
    • Labels
    • Priority
    • Resolution
    • Security level
    • and all option based custom fields that are supported

Due to technical limitations of the current Jira Cloud plattform, only the global context is supported when selecting values for option based fields.

Select the user that will be used to execute the post function. By default, it is set to the current user that executes the transition.

The configured user must have all necessary permissions to create an issue in the configured context as well as to set all the fields specified.

Use cases and examples