Optional rules - Data Center
Description
Create Issue and Create Sub-task post functions can be configured to create the issue only if certain conditions have been met by the issue which is in transition.
Conditions
Define the conditions under which to create the new issue(s) or sub-task(s). If these conditions are not met, then no issues or sub-tasks are created. If you do not define any conditions, then your issues and sub-tasks are always created when the associated workflow transition occurs. There are two types of conditioning, they are:
Sub-task conditioning - prevents the creation of sub-tasks if the original issue is a sub-task and the configuration indicates not to create a sub-task. It has the optional capability to create a sub-task which is a sibling of the original issue.
Pattern matching conditioning - takes advantage of the find/replace capabilities to provide a very flexible way to condition issue creation based on matching issue information with a regex pattern. Although this is a more complex configuration, it is highly powerful in that it covers a great number of use cases. Pattern matching conditioning includes additional details.
Field | Create Issue | Create Sub-task | Default | Description |
|---|---|---|---|---|
Create if original issue is a sub-task |
| Only create the issue if the original issue is a sub-task. | ||
Sub-task default handling |
| Recommend to not select this option unless needed. Select to have Jira default sub-task create handling applied. Selecting this may override settings provided in the create configuration like setting fix versions. Defaulting behavior is similar to how sub-tasks are created from the UI. Example scenarios where you may need this:
| ||
Condition 1 |
| Using substitution variables, you can specify a value or exact match. | ||
Condition 2 |
| Using substitution variables, you can specify a value or exact match. If both Condition 1 and Condition 2 are specified then both conditions must match in order for the issues to be created. The conditions are ANDed together. | ||
Regular expression pattern |
| Specify a regex pattern for conditional matching. The pattern is applied to the Condition field to the left (e.g., Condition 1, or Condition 2). | ||
Exact, Literal, Negative |
| Specify how the regex pattern should be evaluated.
|
Configuration
Define additional configurations for the issues or sub-tasks being created.
Field | Create Issue | Create Sub-task | Default | Description |
|---|---|---|---|---|
Acting user | The user logged in who is transitioning the workflow | Set a user who would have the same permissions as the Assignee for issue being created. This provides the flexibility to the specified user to perform the workflow transition. When you select None for this field, Acting user is defaulted to the user transitioning the workflow. | ||
JQL query |
| Define a JQL query that can be used to populate substitution substitution variables that can be used within individual fields or conditions and regular expressions. The substitution variables include:
| ||
Create multiple issues |
| Using substitution variables, you can specify a value or exact match to create multiple issues. See: How to create multiple issues. | ||
Regular expression pattern |
| Specify a regex pattern for conditional matching. The pattern is applied to the Condition field to the left (e.g., Condition 1, or Condition 2). | ||
Exact, Literal Negative |
| Specify how the regex pattern should be evaluated.
|
Need support? Create a request with our support team.