Anyone else seeing inaccurate On Track / Off Track indicators on Releases?
Asked by Andrew Frayling:

Hi,

We're seeing an issue were if we use rolled up dates for Epics or Requirements then the Release those Epics or Requirements are related to will incorrectly show as On Track at the top level, but correctly show Off Track if you drill through the Release.

Our hierarchy is Requirement -\> Epic -\> Story and we have Requirements flagged with specific releases, but the Epics and Stories are not necessarily flagged with the same release (trying to avoid having to set fix versions on everything and have Advanced Roadmaps roll things up).

If the Requirement uses a rolled up date from the Epics / Stories that is past the release date of the release it will incorrectly tell you your release is On Track at the top level and only show you it's off track if you drill through.

![rolled-up-incorrect-behavior.png](https://community.atlassian.com/t5/image/serverpage/image-id/277229iED35BAC996B9BE43/image-size/large?v=v2&px=999 "rolled-up-incorrect-behavior.png")

Drill Through

![drill-through.png](https://community.atlassian.com/t5/image/serverpage/image-id/277230i81B42D1457FEA53E/image-size/large?v=v2&px=999 "drill-through.png")

If we set an explicit date on the Requirement that aligns with the rolled up date then it correctly shows the release as being Off Track at the top level.

![set-date-correct-behavior.png](https://community.atlassian.com/t5/image/serverpage/image-id/277231i7B41174AE2A8F8E0/image-size/large?v=v2&px=999 "set-date-correct-behavior.png")

Is anyone else seeing this behavior?

If you remain on the plan page without navigating away or refreshing the page then you do see the correct behavior, but if you navigate away with a rolled up date and come back, or refresh the page, or someone else opens the plan then you see the incorrect behavior. E.g.

1. Set an end date on the Requirement that's AFTER the release date for the release - status correctly shows Off Track

2. Clear the end date on the Requirement so it's using a rolled up date that's AFTER the release date of the release - will still correctly show as Off Track

3. Save the change to Jira - will still correctly show as Off Track

4. Refresh the page / navigate away and back / someone else opens the plan - will incorrectly show as On Track

I see the same behavior at every level in the hierarchy. This example is Requirement -\> Epic, but I see the same with Epic -\> Story as well. If the Epic is flagged against a release, but using a rolled up date from the Story then the release will incorrectly show as On Track even if the rolled up date is past the release date.

Thanks,

Andrew.


Answers:
author: Andrew Frayling
body: Atlassian confirmed this is a bug <https://jira.atlassian.com/browse/JSWSERVER-21927>


author: Marc - Devoteam
body: Hi [@Andrew Frayling](/t5/user/viewprofilepage/user-id/781485)

I'm not sure, but this is how I interpretate it.

You have a hierarchy set in advanced roadmap with the "Initiative" as the highest level in this plan.

I think as its part of the release the highest level needs a date to do the roll-up and that is used in the release view.

Thats how I explain it, but to be sure I think reaching out to Atlassian would be a point to see if this might be a Bug

comments: author: Andrew Frayling
body: Hi [@Marc - Devoteam](/t5/user/viewprofilepage/user-id/3796976) , Atlassian just came back this morning that this is a confirmed bug <https://jira.atlassian.com/browse/JSWSERVER-21927>

Glad I wasn't going crazy. Think our workaround will be to tell people to set hard dates on Initiatives / Requirements to get accurate release indications at the top level and then monitor for warnings if underlying Epics and Stories start pushing out and cause a child to have a later end date than its parent.


Tags: advanced-roadmaps

server