Why does JIRA Portfolio show past releases as overbooked and with future dates?

I created a cross-project release and included 3 projects.  Once all the issues were Done and the release went out I went into each project and marked the fixVersion as Released.  However, back in Portfolio it still shows a red flag (overbooked?) and a projected future release date.

If I drill into the 3 projects from the Portfolio release, it shows that one of the 3 is overbooked and has a future projected release date.

What do I need to do to get Portfolio to accurately reflect that the release went out and all the work is done?

1 answer

0 votes

Hi @John Price


I would encourage marking as Done or re-assigning to a different version any issue currently NOT "Done" and assigned to a released version as this ends up being a confusing situation.

It is also possible to exclude a version, which will exclude any issue assigned to it as well and avoid this type of situation.

Finally, while Portfolio keeps "Released" version around, it will not show "Archived" versions.




Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Jira

How you can achieve compact and easy-to-maintain workflows in your JIRA( Server)

This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...

194 views 0 0
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you