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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How is Release Status( on track/off track) calculated?

How is Release Status( on track/off track) calculated?

We are currently using portfolio version 3.6.

 

We have 2 issues in a release, 1 in todo status and 1 in progress status, but the release end date has already passed but it still shows on track.

 

My assumption is that because the date has passed and there is still work to be done that the release would reflect off track.

1 answer

0 votes

Hi Diego,

Thanks for letting us know. The is definitely an issue and the past release shouldn't be shown as on-track. This is already in our roadmap and planned to be fixed.

Regarding how the release status (on-track/off-track) is calculated, here is the explanation.

Release status is calculated based on the target dates of any issues assigned to the release. Here are the definitions:

Released - If the release is Released (i.e. released in Jira) then it's status is not calculated. The release status is only calculated for the Unreleased releases.

On-track - If the all issues assigned to the release are starting and finishing before the release date then the release is on-track. Also if there are no issues assigned to the release or none of the issues assigned to the release has dates then also it will be on-track.

Off-track - If any of the issues is starting or ending beyond the release date then the release is off-track.

Just note that currently the issue status is not taken into account and the release status is purely calculated based on the target dates set on the issues assigned to it. We are trying to improve this behavior, so keep following the documentation.

https://confluence.atlassian.com/jiraportfolioserver/managing-releases-952623605.html

I hope this helps, let us know if you have any further questions.

Regards,

Portfolio for Jira 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Advanced Roadmaps

Introducing Advanced Roadmap’s new dependency report

To see this feature in action check out our recent dependencies demo here: https://www.youtube.com/watch?v=eQu5VsUqyZA Keeping on top of your dependencies is a key part of ensuring project success....

150 views 2 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you