Page History

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

Select the issue type to be created.

The following options are available:

• Selected issue type

• Parser expression (standard issue type):

  UI Text Box
  type info
  Expects an issue type ID or reference a field code like %{issue.issueType.id}

  
  

• Parser expression (sub-task issue type):

  UI Text Box
  type info
  Expects a sub-task issue type ID or a reference a field code like %{issue.issueType.id}

  
  

Choose the parent issue under which you want to create a 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 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:

  UI Text Box
  type info
  The input has to be a project ID or a reference or a field code like %{issue.project.id}

  
  

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

Enter plain text and optionally use field codescode, e.g. %{issue.summary}, to insert field valuesdescription} 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

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

  Excerpt

  Expand title more info.. UI Text Box type info 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" Multimedia name affects-versions-id.mp4 width 700px

• Set field value manually (parser expression) - Read more about parser expressions.
The third 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 (Affects version/s, like Affects- or Fix version/s)
• Component/s
• Labels
• Priority
• Resolution
• Security level
• and all option based custom fields that are supported