.png?version=1&modificationDate=1657805719617&cacheVersion=1&api=v2&width=272&height=48)
2013-04-19
Highlights
Create Multiple Issues or Subtasks
This ability to create multiple similar issues or subtasks with one configuration is especially important when the number to create is dependent on information from the original or parent issue. For example, creating one subtask for each fixed version for an issue. See How to create multiple issues or How to create multiple issues - advanced example for more details.
JQL Query Substitution Variables
An option to run a JQL query has been added. The results of the query can be used as substitution variables for conditioning, setting field values, and creating multiple issues. How to create multiple issues - advanced example shows how this can be used.
| Variable | Description | Notes |
|---|---|---|
| jql_result_count | Number of issues returned by the query | |
| jql_result_list | Comma separated list of issue keys returned from the query | |
| jql_result_n | The issue key for the nth issue returned from the query where n is a number | Blank if n is not in range for the issue list |
Group and Role Substitution Variables
Additional substitution variables that can help with conditioning, setting field values, and creating multiple issues.
| Variable | Description | Notes |
|---|---|---|
| group_<group name> | Comma separated list of user ids for members in the group | Example: group_jira-users |
| role_<role name> | Comma separated list of user ids for users that are role actors for the project of the original issue | Example: role_developers |
| user_id | User id of the user that initiated the transition |
Improvements and Fixes
- Fix for sibling create getting wrong parent.
- More consistent and documented substitution variables.
- Support multi-line custom fields.
- Allow ids for issue security lookup.
