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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Delivery progress - take into account child issues

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

2 answers



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.
0 votes
Rohan Swami
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 16, 2023

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.pngScreenshot 2023-05-16 at 1.52.49 pm.png

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

We are using the following structure. 

- Deliverable
-- Epic
--- Task/Story

Screenshot 2023-05-16 at 17.33.08.png

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.
Like Katja Arendt likes this
Rohan Swami
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 17, 2023

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:

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events