You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Trying to build a Plan for all Issues assigned to a particular set of individuals, so we can see a holistic view of the work.
Have built a JQL Filter along the lines of:
Assignee = X OR Reporter = X OR Epic = Y OR ParentEpic = Y
This returns all the relevant issues.
However in the Plan, a Subtask sometimes does not display if it has Parents missing from the above Filter output.
Essentially want to see the hierarchy of Issues wherever any single Issue in the hierarchy is Assigned to X, else show nothing.
As you're on Jira Cloud, the correct answer is to get an app that provides JQL extensions you're looking for.
With standard JQL, you can only get a list of issues and export them to Excel for further processing. This works if you want to do a one-off analysis. Your use case is more dynamic than that.
Standard JQL doesn't easily allow it but you can quickly found using our professional indexing service:
After you install the app, you can simply search:
assignee=currentUser() OR issue in parentsOfIssuesInQueryRecursive("assignee=currentUser()")
The query supports Jira Advanced Roadmaps (Portfolio).
Check out the documentation for more examples.
I hope this helps!
I can see how this could get tricky, just using JQL. especially trying to pull the whole hierarchy from a sub-task level.
Question: Is this work always going to be with a single Jira project? or could X be reporting and assigned to work across lots of different Jira projects??
What I'm thinking is, it might be easier to filter a broader dataset into the plan and then filter and create a view of the X related work.....that way the hierarchy would (or at least could) be there without the need for such complex JQL.
Hi @Curt Holley
X will be Reporting and Assigned work across multiple Jira Projects.
Yes I take your point about bringing in a wider Issue-set and then filtering, it's just that the wider Issue-set is very wide... We already have that, just trying to build a new view of the work.
What we ideally want is the inverse of:
issuekey in portfolioChildIssuesOf("Issues_Assigned_to_X")
I.e. go up the hierarchy from a Child, rather than down from a Parent.
Do you have any ideas why some of the Subtasks returned by the Filter are not displaying in the Plan? It is happening when the Parent Story of the Subtask is not Assigned to X. I would have expected them to appear as Issues without Parents at the bottom of the Plan, rather than not appear at all...