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

Receive Indicator That Release is Off Track. What does this Mean and How Do I fix?

John Bacon_n9z8hl

When creating my roadmap in JIRA, I noticed a warning indicator that states my releases are off track as shown in the screenshot. For example in the screenshot it shows my May release is off track by 3 days and my June release is off track by 4 days. I don't understand what this means, how JIRA is determining this or how to fix it.

Screenshot 2022-05-20 095342.jpg Screenshot 2022-05-20 095452.jpg

Accepted answers

Michael Andolfatto_a62ntx

Hi @John Bacon ,

Releases in Jira's roadmaps can be thought of as deadlines when they have a Release Date set. This is saying that all issues assigned to Release X need to be completed before X date to have the release be considered "on-track".

Currently, Jira is telling you that you are off-track by three days because the team(s) you have created to work on the issues do not have enough capacity to resolve everything in the given timeframe. - An example would be that you have one team with a capacity of 40 hours that is trying to complete 50 hours worth of work in an iteration.

To amend this, you can do a few things:

Push back the release date (modify time)
Increase your team's capacity (modify resources)
Move some issues into a different release (modify scope)

These are the three corners of the Iron Triangle which is an interesting concept when working with Agile projects.

All comments

Michael Andolfatto_a62ntx

Hi @John Bacon ,

To amend this, you can do a few things:

Push back the release date (modify time)
Increase your team's capacity (modify resources)
Move some issues into a different release (modify scope)

These are the three corners of the Iron Triangle which is an interesting concept when working with Agile projects.

John Bacon_n9z8hl

@Michael Andolfatto I looked at the road map, and it shows there are only 13 story points in the release, but my teams Sprint Velocity is set to 30 points. So why is it telling me my release is off track, if the work is less than the teams sprint velocity?

John Bacon_n9z8hl

@Michael Andolfatto Something else that doesn't make sense is when I filter to only show the issues that are part of the release, the story point rollup to the epic level, story points don't add up as you can see in the screenshot. For the epic it shows 13 points, however the total points for the stories in the epic only add up to 7.

Screenshot 2022-05-20 114049.jpg

Michael Andolfatto_a62ntx

@John Bacon if you filter your roadmap to only display issues assigned to your May release, you should see at least one issue which extends past the vertical marker (May 20th according to your screenshot)

All issues assigned to your May release need to finish prior to this deadline. If using Advanced Roadmaps, the auto-schedule button can automatically fix this (if you let it overwrite sprint dates) or else you can manually specify the start/end dates by changing the sprint the issues belong to, or the date fields that affect its scheduling. (This should also be able to be done by manually dragging the issues left)

If it fails to update as written above, then there may be some other issue responsible - e.g. Issue A which has a Blocker relationship with Issue B, that prevents Issue B from being completed earlier.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server

roadmap