Release of Portfolio Cross-Project Release

Hello,

I've started using Portfolio for a few months and now that we've reached release time I wonder how to actually use the cross-project release feature (CPR) to close the CPR and the individual releases (or versions in Jira).

It's fairly straitforward to create a CPR and to link it to individual releases for the projects in the plan. Even the "align date" is pretty nice when some deadlines shift. But how am I supposed to handle the fact that a release has been done and that the CPR has to be released?

In Jira, one can release a version and automatically re-assign open issues to another selected release but it doesn't seem to be possible to do the same with a CPR. Am I suppose to release the individual releases one by one? How can I keep the release in the plan for further reference and indicate it as done?

I also found that even though some release dates are overdue (e.g. 31-03-2017), Portfolio keeps on adding issues to those releases and complains that they are late. Is this a bug ? It seems obvious to me that doing so will result in an overbooked release.

Thanks in advance for sharing your experience,

Stephane

1 answer

0 votes

Hi Stephane,

Yes, you will have to release your releases individually from within JIRA. This release process is quite complex and includes checks and wizards to decide what needs to be done with unfinished issues assigned to a release at time of closure.

That issues can still be added to a release is related to the release status rather than the release date. In JIRA you would formally release a version, which updates its status to 'released'. As from that moment onwards, it is considered to be done and issues will no longer be added.

Hi Walter,

I have the same Problem (I think) but your solution did not work for me. I have

  • created a cross-project-release X in two projects with a planned release date that is in the past,
  • then released the individual releases in JIRA,
  • then hit "calculate" in Portfolio and still have an issue that get's auto-assigned to the closed cross-project-release X instead of the still open Release Y.

The issue in question has a remaining estimate of 1 day. If I set this to 2 days the issue get's assigned to the correct release Y. If after doing this I double the team capacity the issue get's assigned to the closed release X again. If after doing this I set the issue's remaining estimate to 3 it get's assigned to the correct release Y again.

It would be great if you could help with this.

Thanks in advance
Gunnar

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,782 views 11 18
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot