I’m stuck trying to create a JQL query for our Jira Server 9.12. What I need is to see all the issues and their subtasks within a particular epic. This epic has tons of issues, each with its own set of subtasks.
I’ve looked online, but most solutions only work for Jira Cloud. We’re using the server version, so those don’t help. My end goal is to save this query as a filter and use it for a dashboard. This way, I can easily monitor all the work happening in the epic.
Has anyone tackled this before? Any tips or tricks would be super helpful. I’m pretty new to JQL, so even basic advice is welcome.
hey there! i’ve dealt with this before. try this JQL:
‘epic = EPIC-KEY OR issuefunction in subtasksOf(“epic = EPIC-KEY”)’
replace EPIC-KEY with ur actual epic key. this should grab all issues and subtasks in the epic. works great for dashboards too. lemme know if u need more help!
Based on my experience with Jira Server, here’s a solution that should work for you:
JQL: ‘epic = EPIC-KEY OR parent in (epic = EPIC-KEY)’
Replace EPIC-KEY with your actual epic’s key. This query will fetch all issues directly in the epic, plus any subtasks of those issues.
For your dashboard, save this as a filter. It’s efficient and won’t slow down your system, even with large epics.
One thing to note: this approach assumes your subtasks are directly linked to issues in the epic. If you have a more complex hierarchy, you might need to adjust the query.
If you need further customization, consider using the ‘issueFunction’ as well, but be cautious as it can impact performance on larger datasets.
I’ve tackled this issue before, and I can share what worked for me. For Jira Server 9.12, you can use a combination of ‘issue in linkedIssues()’ and ‘issueFunction’ to get what you need.
Try this JQL query:
project = YourProject AND (issueFunction in linkedIssues(‘key = EPIC-123’) OR issue in linkedIssues(‘key = EPIC-123’))
Replace ‘YourProject’ with your actual project key and ‘EPIC-123’ with your epic’s key.
This query will fetch all issues linked to the epic, including subtasks. It’s been reliable for me in creating dashboard filters.
One caveat: if you have a massive epic with hundreds of issues and subtasks, the query might be slow. In that case, you might need to optimize or break it down further.
Hope this helps! Let me know if you need any clarification.