Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

when grouping by components on jira advance roadmaps it doesn't bring in the child tickets.

Kaushal Patel
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 20, 2022

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?

1 answer

1 accepted

0 votes
Answer accepted
Curt Holley
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 20, 2022

HI @Kaushal Patel 

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.

Unnikrishnan Ramachandran April 22, 2022

@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?

image.png

Curt Holley
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 25, 2022

@Unnikrishnan Ramachandran So is it not that the stories do not have the release in the fix version field?

Unnikrishnan Ramachandran April 25, 2022

@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.

Like Curt Holley likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events