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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
My issue is in the management of many suppliers mixed into one project to deliver a very complex product, so everything needs to be in a the same project, the Epics created for a new launch are then labelled to denote that they are needed for a launch and are not ongoing product improvements, however some can also be product improvements so they are part of current sprints/components etc.
As such labels on Epics have become invaluable in zoning in on each suppliers Epics that are required for a new launch, but I can't find a good way to set up a board to track the Story tickets in the labelled Epics.
I am using JIRA Cloud and am looking to find a way to do this (see code sample), but without the plug-in as it is not available for Cloud instances.
issuefunction in linkedIssuesOf("filter = MyEpicFilter", "is epic of") OR filter = MyEpicFilter ORDER BY Rank ASC
As I have a filter set up to capture all the Epics labelled with "launch" and from that I then essentially want to invert this so I can view all the 'children' of those Epics, the story tickets, so I can then set up a Board to track it and also pull it into a Confluence page for other stakeholders to easily view.
Thank you to anyone that can help shed some light on this.
attempting to clean up old posts. What about using Automation to add the label to any issue added to the epic?
This has been a number of years!
In answer to your question and to resolve this old posts, Automation wasn't available in the instance I was using at this time.
This problem has since been solved by the usage of Advanced Roadmaps/Plans on Jira that allow tickets to be grouped per team. So thank you for checking in on a old unanswered question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.