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
We are using Advanced Roadmaps to view large programmes of work and one huge piece of work will span multiple programmes (a Programme or Programmes). So - I was hoping to link the programmes together (using the standard link functionality) and create a query that will bring back all the children tickets and the top level Programmes that make up the Programme of Programmes.
One Programme will be the master with 3 or 4 programmes linked to it (lets say using "child of" links)
PROG-1 will be the master.
Bear in mind we are still using Jira DC until mid 2024 - so we are using ScriptRunner for DC.
I know I can use issuekey in childissuesof("UKIPROG-1") or issuekey in childissuesof("UKIPROG-2") etc.
But this depends on altering the filter if new Programmes are added and it would be easier to get them to just add a "child of" link to the Programme up to PROG-1
I am also aware that we could put another layer in the Advanced Roadmaps hierarchy but the business wants to avoid that as we already have quite a few layers.
I have had a quick look at nesting JQL and it broke my brain - so posting here.
Hi @David Semmens ~ maybe I'm not fully understanding why issue in (childIssuesOf(PROG-1)) OR key = PROG-1 won't work. If PROG-1 is your master and will have Programmes linked to it, it should give you that full hierarchy when new links are added.
You could also use issuefunction in porfolioChildrenOf("key = PROG-1") or some other sub-query instead of "key = PROG-1". That allows more flexibility rather than using just key values for your hierarchy search.
Thanks Laurie - My question wasn't totally clear - so apologies. I was looking for a way to gather the details of all tickets that sit under multiple Programmes without having to specifically name each programme in the query.
So - if Prog-1 was always the master but this was linked using something like a "Depends on" link (not in the hierarchy of Advanced Roadmaps) then people could create a programme of programmes by sideways linking them to the master.
I did try sideways linking using the "Child of" standard link that we have but this didn't work using.
After much discussion the business has agreed that we should just add another layer to the hierarchy so we can easily see the programme of programmes in Advanced Roadmaps and more easily query the data.
I still need to figure out nested Script runner JQLs though as they would prove useful.
I will accept your answer as you did spend time replying :) Thanks
Ah ~ I see! Have you tried issue in linkedIssues("PROG-1")? That should give you all issues linked to PROG-1, regardless of the link type. That wouldn't give you external web links or links to Confluence pages, but that can be done as well ~ not sure if that's needed for this use case though. HTH, @David Semmens !
That only brings in the tickets directly linked to PROG-1. What I needed was a nested query that used issue in linkedIssues("PROG-1") to find all the other PROG tickets linked to the master and then with that result to find all child tickets of the PROGs list.
All good now anyway - We are moving to another layer above Programme :)