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

Add multiple releases of a same project into a cross-project release in Portfolio

I need to create a cross project release which shall include several releases coming from the same project.

It seems that by default there can be only one release per project: as soon as I have added a release from a project, this project is colored in gray and is not longer for selection when I want to add another release into the cross-project release.

Can you someone help please?

Thanks

Nghia

1 answer

0 votes

Hello @nph ,

The Logic behind the restriction is that a release is a compartmentalized piece of each project, and if you have the ability to combine issues from multiple release within the same project at the same time they should already be lumped together into a single release, and not be separated into alternate sections, the Releases are intended to be Sequentially released mutually exclusive chunks of data.

This is noted in the Cross Project Release documentation in the section "How to add an existing release to a cross-project release" at point "4" stating:

4. Select the release you want to add. Keep in mind that you can only have one release from a project in the cross-project release.

Regards,
Earl

I have read this logic, but I disagree with it. We have many components (essentially microservices) that are maintained in a single Jira project (essentially a team). Each of those components have their own versions and we track those using Jira Releases individually. For example, I have 

Component A

Component B

I may have the following Releases:
Component A-1.0
Component A-1.1
Component B-3.1
Component B-3.2
Component A-1.2

And I oftentimes want to group one or more of them into a single overall release which I want to use Jira Advanced Roadmaps to track. With the current limitation of only allowing a single release from a project, there is no way to display this in Advanced Roadmaps. I would ask you to please consider adding this feature.

Also, we typically have many components (20+ per Jira project) each with their own versions. To distribute each of those into their own Jira project would be impractical.

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....

148 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