Jira Big Picture JQL: How can I retrieve subordinate issues without defined links?

How can I query fourth-tier issues under a selected third-tier issue without explicit linking?

FIND project=ABC AND parentTask('Task3')

i had similar issues. if u have scrpt runner use: issueFunction in subTaskOf(‘key=Task3’) to get lower tier issues. standard jql wont fetch 4th-tier recusrively, so plugins help out.

Based on my experience managing hierarchical issues in Jira, the challenge of retrieving deeply nested issues is best solved with automation through plugins or custom scripting. In a recent project, I encountered similar needs and ended up using a flexible custom plugin approach that allowed me to simulate recursion by using a combination of script runner and dedicated automation rules. This method provided a sustainable and efficient solution to capture subordinate issues beyond the third tier, without the need for explicit linking or manual intervention.

I have encountered a similar challenge in the past and found that when standard JQL does not provide the necessary depth, incorporating an external script using Jira’s REST API can be a viable workaround. In one project, I wrote a script that made recursive API calls starting from the third-tier issue to collect all subordinate issues without explicit links. The process required some initial development effort but ultimately delivered a flexible solution that bypassed the inherent limitations of standard JQL.

i tried a recusrive rest api approach for this. built a tiny script that looped thru each level till no new child tasks were found. it’s a bit hacky but it worked for my needs. hope that helps

In my experience, the key to working around JQL’s limitations is to design a solution that periodically collates hierarchy data using Jira’s available APIs. I built a small integration that pulls all child issues recursively based on parent identifiers and then writes a summary into a custom field. This approach allowed me to run standard JQL queries on that custom field to find deep-tier issues without explicit linking. While it required some initial development effort and regular maintenance, the solution provided consistent, real-time updates of the issue hierarchy and ultimately streamlined our tracking process.