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.

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}

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 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}

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.

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"

  
  

  • 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:

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