nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Roll-up seams to not work in Dependency reporting

Vilhelmine

Hi there,

I have multiple teams working in Jira and we have been trying to roll out the Advanced road maps to track progress and dependencies of the Deliveries. Needles to say it has not been easy and we still have a lot to do.

My issue with the Dependency view, is that currently even thought I try to Roll up to Epics I can still see all the Stories and Tasks and dependencies between them, but not a roll up view. We have also introduced an Initiative in the issue hiarchy to be above Epic, but no matter what Roll-up option I choose, the Stories are still there.
I checked that though part of plan, those particular Stories do not belong to any Epic - does it mean that first we need to get every single Story under an Epic, to get the roll-up function in the Dependency view to work?

Any help or explanation how to fix this is much appreciated

With kind regards,

Vilhelmine

Comments

Curt Holley

Hi @Vilhelmine

Welcome to the community!

I'm not entirely sure I know which view you are asking about. Do you mean the pre-set "Dependency Management" view? or the "Dependencies Report"??

If the former, unticking "Show full hierarachy" should tidy up that view.

For stories not linked to an Epic, it is true....they logically have nowhere to roll-up to. So yes, to roll them up they would need to be linked to an Epic.

If you could share a screenshot of exactly what you are referring to, that would be helpful for the community to further assist.

Regards

Curt

Vilhelmine

Hi Curt

Thak you for responding so fast - I was not aware of the Dependecy management view, but I should have included a screan shot from the start
I'm referring to Dependency report view. dependency example.jpg

In this smapshot, I checked and the OMNI-514 and OMNI-525 actually belong to an Epic, yet, they are still not rolled up to it.

Is it possible to somehow choose which dependencies/links I would like to see - for example, Cloned tickets are not relevant for this view, and there are a lot of those which is just cluttering the view.

Curt Holley

Hi @Vilhelmine

Are the Epics visible in the Plan? as that doesn't appear to be rolling up at all.

How different is the view when not "rolled-up"?

Regarding which dependencies you can view. That is set globally in the Advanced roadmap settings and cannot be further filtered in the Plans/Dependency report. I like the idea though, you should give that feedback to Atlassian via the "Give feedback" button

Vilhelmine

Hi @Curt Holley

Yes, in the plan, I have Stories , Epics and Epics linked to Initiatives by Parent link. And it seams that the view stays the same if I roll up or not. Could this be a bug and maybe I should reach out to Atlassian?

matt_jay

I am facing the exact same issues. With some experimenting based on what configuration options there are for plans, I found out that the roll-up was working for a plan that was based on a project as an issues source, and didn't work fpr a plan based on a filter. When I switched the source of the filter-based plan to a project instead, the roll-up worked.

Might there be limitations when dealing with filter-based plans?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

advanced-roadmaps