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; } } }

Delivery progress - take into account child issues

Matt Jones_uhtii2

Currently, the Delivery progress bar only seems to take into account the issues that have been directly linked to an idea, and not its child issues.

ie. Link a new feature to a Deliverable in JIRA Advanced Roadmap that has child issues as Epics and Stories in the various JIRA software team projects.

The Delivery progress bar show only one ticket linked and so status as complete which is very misleading. Alternatively, you would have to link EVERY single ticket which seems to defeat the object of having child issues with parent links.

Screenshot 2023-05-16 at 13.24.08.png

Accepted answers

All comments

Rohan Swami

Hi @Matt Jones ,

There are 2 options for calculating Delivery progress which you can see when you click on "Edit field":

Simple - Searches linked issues only for the calculation.
Default - Searches 1 level down to calculate progress. The limitation here is that we don't go down further levels for performance reasons. Do you need to aggregate from levels even further below?

Screenshot 2023-05-16 at 1.52.19 pm.png

agileautonomy

Hi,

AFAIK JPD and Advancd roadmaps calculate the Deliver Progress one level down regarding the topmost issue.

I wish we could configure how Delivery should be calculated.

In a nutshell, I would like to

rely on Advanced Roadmaps or Atlas issues at the top level and link them to JPD issues
be able to define the depth taken into account
set custom Delivery categories based on Jira projects and/or issue types so I can distinguish preparation etc. work from software implementation and any follow-up activity.

Matt Jones_uhtii2

I had seen the different options but thank you for explaining.

We are using the following structure.

Initiative

- Deliverable

-- Epic

--- Task/Story

We were linking some big ideas to Initiatives so using Default looks like it will only get one level down to Deliverables which won't take account of the Epics at team level. Would benefit from being able to get 2 levels down or at least have the option to do so, even at the expense of performance.

Alternatively, we may just need to break our ideas down further to avoid mapping to Initiatives and only map to Deliverables or Epics.

Rohan Swami

Thanks Matt. Would you be interested in speaking to us in a bit more detail about what your use case so we know what solution would work best for you? Here's my Calendly: https://calendly.com/rswami-atlassian/customer-calls

Hollie Dalton

I have the same problem. Our hierarchy is Initiative -> Epic -> Story. We typically have lots of epics beneath each initiative and it would be a nightmare to try to keep up with adding each epic as a separate delivery ticket in my Discovery Ideas. It would be great to be able to aggregate progress from two levels down as progress at the story level is really what would tell the true progress story for us @Rohan Swami

Etienne CHATAIGNIER_m4dqbu

We have exactly the same needs.

Vishakha Dahra

I am struggling with the same problem. I want the story points to be aggregated from 2 levels down, not just one level.

Our hierarchy:
Initiatiave> Epic> Story

Kim Alders

Hi Rohan

Is this available to anyone?

I am using epics in a teammanaged board. The epic contains stories. Some of the stories have storypoints.

I do see the possibility in project planning to set progress to default. And if I set it to number of tickets, it works, but if i set it to story points, it does not. It just shows one gray line.