Automation rule to limit the scope of search to current parent issue only
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Consider a scenario where a parent issue has multiple child issues. When a subtask is closed, an automation rule is triggered. The rule uses a JQL to identify subtasks based on the summary. The scope of the search includes all the sub-tasks from the instance. We don't have an option to restrict the search for the current parent issue.
Example:
- There is a parent task ABC, That has 25 Sub-tasks named (S1, S2.....S25).
- Subtask S2 is closed, automation rule is triggered. The rule searches all subtasks that have the same summary as S2.
- The requirement is to limit this search. The rule should search only the 25 subtasks that are present under parent task ABC
Environment
Jira DC
Solution
- We can create a variable that points to the parent issue.
- Then include the variable in the JQL. In this manner, the search will only take place within the parent issue and not the entire project.
