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

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.


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 sub-task to be created. The following options are available:

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

  • 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
  • Seed issue's project (only available if mode "Multiple issues based on an issue list" was selected)

  • 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 code, e.g. %{issue.summary} or functions provided by the selected parsing mode.


Enter plain text and optionally use field code, e.g. %{issue.description} or functions provided by the selected parsing mode. You can enrich the styling of your description by using the available 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 how to set the value. There are three or - when dealing with selectable fields - four options:

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


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. 

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.


The configured user must have all necessary permissions to transition the target issue.





Use cases and examples