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.
when grouping by components on jira advance roadmaps it doesn't bring in the child tickets.
is there a workaround for this or does the component need to be added to each project and each ticket?
Yes, for anything to appear in the grouping, it has to have the relevant field populated (in your case, component).
You could set up automation to populate components on to Stories etc from their Epic, but that still requires the Epic having the data.
@Curt Holley I have the similar issue when Grouping By Releases.
It brings the "Epics" under a release, but does not bring the "Stories" under the Epic.
Any suggestions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Unnikrishnan Ramachandran So is it not that the stories do not have the release in the fix version field?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Curt Holley Thank you! that helped. I was assuming that the Epic - Story relationship would implicitly tie the stories to the Fix Version field.
I explicitly updated the story to have "Fix Version" and it worked.
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.