Delivery Status by Epic
Asked by Jackie LaFrance:

Hi there! When I started working in JPD, I linked all of our backlog epics to ideas and could see the rollup by story or bug under the epic on the idea card. Something changed sometime last week, and now I can only see the number of epics. Obviously, this isn't showing a good view of the outstanding work we have before an idea can be released. I've tried unlinking and relinking the epics, and that didn't solve the problem.

Is this a sign that something broke in development, or is this the way delivery status will be communicated going forward?


Answers:
author: ?kos Botos
body: Hi [@Martin Sturm](/t5/user/viewprofilepage/user-id/216097) or [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312)

Something funky is going on on the Delivery tab.

**Video:** <https://www.loom.com/share/3d072244da1442a3b42c391590393d98>

**Description**

* Idea with 2 JSW tickets added
* Adding the Parent Epic of the issues
* All good 2 original issues and the Epic is displayed under Delivery
* Expanding the Epic on the Delivery tab makes the already attached issues disappear
* Refreshing the page restores the expected view

*Somewhat related*

Might be related this that for a while the Expand arrow is present next to all issues even in the case of stories without subtasks.

comments: author: Martin Sturm
body: Hi [@?kos Botos](https://community.atlassian.com/t5/user/viewprofilepage/user-id/4724462) - thanks for the bug report! We recently changed the issue hierarchy component and this bug slipped through.

The one with the expansion arrow is a known UX degradation of this new component and you are by far not the only one annoyed by this ? I hope we can fix this soon.


author: ?kos Botos
body: [@Martin Sturm](/t5/user/viewprofilepage/user-id/216097) from now on please contact me through this profile.

Cheers,

?kos


author: Rohan Swami
body: Hi [@Jackie LaFrance](/t5/user/viewprofilepage/user-id/5104919) to help diagnose the issue can you help me understand how what you're seeing is different to the screenshot from my demo instance below?

![Screen Shot 2022-12-19 at 9.45.14 pm.png](https://community.atlassian.com/t5/image/serverpage/image-id/231257i7C59146280DE06B6/image-size/large?v=v2&px=999 "Screen Shot 2022-12-19 at 9.45.14 pm.png")

comments: author: ?kos Botos
body: We have the same problem. The progress seems to be calculated only based on the top two levels e.g. Saga/Super Epic. Everything below is ignored.


author: Tanguy Crusson
body: [@Jackie LaFrance](/t5/user/viewprofilepage/user-id/5104919) [@?kos Botos](/t5/user/viewprofilepage/user-id/4724462) we had changed something in the implementation last week and this looks like a bug with that. We've reverted the changes for now while we're investigating. Is it working for you now?


author: Jackie LaFrance
body: [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312) - yes, it's working this morning. Thanks for the fix!


author: Martin Sturm
body: Hi [@Jackie LaFrance](/t5/user/viewprofilepage/user-id/5104919) [@?kos Botos](/t5/user/viewprofilepage/user-id/4724462) - I am an engineer on the team and we are still struggling to reproduce the issue that you experienced.  
Would anyone of you be willing to either get on a short call or asynchronously answer a few questions that might help us here understand the problem?


author: Jackie LaFrance
body: Hi Martin,

I don't know what time zone you're based in, but I'm in Eastern time (USA). I can hop on a call most afternoons or answer questions async if that works better for timing.


author: ?kos Botos
body: Hi [@Martin Sturm](/t5/user/viewprofilepage/user-id/216097)

I can show you an example and answer your question. By any chance a deploy related to the forthcoming change of Parent/Epic link handling could cause this?


author: Martin Sturm
body: Thanks for your responses [@Jackie LaFrance](/t5/user/viewprofilepage/user-id/5104919) and [@?kos Botos](/t5/user/viewprofilepage/user-id/4724462)

We currently have the same suspicion as you [@?kos Botos](/t5/user/viewprofilepage/user-id/4724462) - I am currently removing some deprecated things from our code and would love to verify it resolves the problems you are experiencing.

If this is fine with you, I will reach out again when the changes are ready.


author: Martin Sturm
body: Hi [@?kos Botos](/t5/user/viewprofilepage/user-id/4724462) [@Jackie LaFrance](/t5/user/viewprofilepage/user-id/5104919) I finally got my changes merged - had a busy week on DevOps rotation ...  
[@?kos Botos](/t5/user/viewprofilepage/user-id/4724462) , reading your profile I am assuming that you are in CET just like me? Would it be fine for you if I enabled the new loading for your instance tomorrow and you let me know if it works? Or would you prefer to check synchronously in a call?


author: ?kos Botos
body: Hi [@Martin Sturm](/t5/user/viewprofilepage/user-id/216097) ,

Yepp, I am at Budapest, Hungary (GMT+1) so I can check this tomorrow. Let me know when to check.

Is there anything to watch out other than the depth of issues JPD calculates the progress?


author: Martin Sturm
body: Hi [@?kos Botos](/t5/user/viewprofilepage/user-id/4724462) ,

delivery tickets loading without deprecated fields is enabled for you now. This shouldn't impact any other part of the app.

Please let me know if this fixes the hierarchy. If not, I might have some follow-up questions :)

Thanks


author: ?kos Botos
body: Hi [@Martin Sturm](/t5/user/viewprofilepage/user-id/216097)

Unfortunately, nothing change for the better.

I did some simple AB testing. Based on that it looks like that JPD works fine when one adds EPICs to the Delivery tab.

However, extra hierarchy layers makes it confused. For example we have a Super EPICs (created via Advanced roadmap) located above EPICs.

At the moment when a SUPER EPIC is added to to the Delivery tab it seems like that the Delivery progress bar doesn't take into account anything below the EPIC level (Story and Sub level). In a more abstract way one level below the issue added to the Delivery tab.

Often we use SAGAs (One extra level) which makes things even worse.

Back around October all was working fine (apart from hittin the 1000 issues).

While we are at messing with this part of the code let me share my feature request I've shared with [@Maja Lukomska](/t5/user/viewprofilepage/user-id/5026134) and hndounga@atlassian.com. Basically it would be great if the users could configure the Top and Bottom hierarchy levels (per JPD project) JPD should display and take into account during the Delivery progress calculations.

FYI [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312)

If you have any questions shoot or drop a Calendly link if you would prefer a call.

Have a nice day,

?kos


author: Martin Sturm
body: Hi [@?kos Botos](/t5/user/viewprofilepage/user-id/4724462) - thanks for the detailed feedback. So there are actually two points I'd like to talk about. The first is the calculation of the progress - I absolutely agree with you that it should go down the whole tree of issues to aggregate, but this is how the progress is calculated in Advanced Roadmaps - two levels down - and we need to be consistent here. Actually I just raised this concern with our PM yesterday :)

The second thing is the hierarchy itself: If you are in the Delivery tab and expand the hierarchy downwards - are you missing any child issues? Also I disabled the loading limit for you to make sure this is not the limiting factor. Because as soon as you hit the limit, unfortunately all bets are off because we cannot aggregate the data correctly anymore on an incomplete hierarchy.

Thanks again, Martin


author: ?kos Botos
body: Hi [@Martin Sturm](/t5/user/viewprofilepage/user-id/216097)

Thanks for the info and lifting the 1000 issues limit.

Regarding progress calculation and consistency. I think Advanced Roadmap would benefit from a calculation with customizable deepth. There is one main difference between JPD and AR. In AR one can drill down to see what is really going on. Still not summing things ump is basically misleading for those relying on the top level info e.g. EXECUTIVES no matter which tool we are talking about. So that is really bad IMHO!

Regarding missing any child issues. I think we indeed did missed child issues on the third level down AFAIR, i.e. EPICs when adding SAGAs (Saga/Super Epic/Epic). Cannot find and example ATM though.