Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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?



3 answers

So any statement by Atlassian people here? 

Allowing this is crucial to successfully plan bigger projects! 

Please think about it and please give some feedback, guys! 

Thanks in advance & bests, 

This is a must have. Jira has components, we can create multiple versions, recommendations for component versioning suggest using component-x.y.z, yet we cannot combine those versions using cross-project releases!

0 votes
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 02, 2020

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.


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.

Like # people like this

Agreed - Atlassian should allow per-component releases from within the same project. Otherwise why do we have components at all if we're required to have a unique project per release?

Like # people like this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events