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 setup hierarchy between projects in order to follow:
- In the high level project (like a parent project) theme / initiative
- In the second level product projects (like a child project) with Epic / Story
In the high level project we add Theme and initiative at the macro level and in the childs projects we decline Epics / Story, etc ... linked to Initiative from parent project
On Epics, we use parent link to declare his parent from parent project
We use advanced roadmap to follow all tickets from "parents" & "child" project but currently I see in advanced all issues from both projects even if issues from child project are not linked to Initiative from parent
I need to have a JQL to find all Epics linked to Initiative from parent project like this:
"Parent Link" in ("project=DCOM")
The project DCOM is the parent project
I find the JQL on this link but it doesn't work (https://valiantys.com/fr/blog/atlassian-administration-fr/jql-guide-recherche-jira/ )
If try with "Parent Link" in (DCOM-35), I have all child issues
Is there a query to list all Epics related to an initiative from another project?
Thank you! :)
I use this JQL,
issuefunction in portfolioParentsOf("key = DCOM-####")
This returns the ancestry of DCOM-####. From there you could add on a pre-cursor function to instead return the descendants of the resulting ancestry like,
issuefunction in portfolioChildrenOf("issuefunction in portfolioParentsOf('key = DCOM-####')"
You could also populate the inner parenthetical with a more complex JQL like,
issuefunction in portfolioParentsOf("Project = DCOM and type = Epic")
but might overload your results.
All that said, I think the issuefunction call is part of the script runner plugin so without that I'm not sure how to do it.