On this page
Introduction
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 and sub-task issue types in the system (excluding next-gen projects).
Additional field values can be inherited or manually set using parser expressions.
The configuration
The table below lists all available parameters that have to (*) or optionally can be set in this post function.
Parameter | Description |
---|---|
Issue type* | The issue type of the issue to be created. The following options are available:
In case a sub-task is chosen, the respective parent has to selected. |
Parent issue (only for sub-tasks)* | Choose the parent issue under which you want to create a sub-task. The following options are available:
The parent issue is only shown when a sub-task is selected as issue type. |
Project (only for standard issue types)* | The project the issue will be created in. It comes with the following options:
Please note that the project selection does not show up when the issue type is a sub-task. |
Summary* | Enter plain text and optionally use field codes, e.g. %{issue.summary} , to insert field values. |
Description | Enter plain text and optionally use field codes, e.g. %{issue.summary} , to insert field values. |
Additional fields | Optionally set additional field values. In the popup after clicking the Add button you can select to set the value in various ways:
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. 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" Error rendering macro 'multimedia' com.atlassian.renderer.v2.macro.MacroException: Cannot find attachment 'affects-versions-id.mp4'
The third option Selected value is available for the following fields:
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 checkbox value, for example, can be set like this: |
Run as | Select the user that will be used to execute this post function (the issue creator). The user can be selected among from these options:
|
Conditional execution | Enter a condition (a logical expression) using the expression parser syntax. You can even logically link and nest conditions in expressions as you like in order to map more complex conditions. The post function will only be executed if the condition is met (returns |
Get started
Get started by trying out the example configurations provided out of the box.
The following example configurations are currently available:
- Create an issue in the current project
- Create a simple sub-task
- Create a sub-task for high priority issues
Additional use cases can be found here!
Use cases and examples using this post function
Use case |
---|
No content found. |