You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi @yuna - By default in Jira, releases (versions) belong to each project only (project specific). Just like components. In Portfolio for Jira, you can roll up your project's EPICs to Initiative, where you can use Initiative to associate with specific releases. Those releases of Initiative can then act like cross projects releases.
In our env, our Initiatives are in a separate Jira project where all other DevOps projects roll up their EPICs to the Initiatives. The releases in this separate project serve as the cross projects releases.
cross-project releases aren't a default Jira functionality.
You can work with them in Portfolio for Jira or you need to use some of the apps on Atlassian marketplace that solves this problem https://marketplace.atlassian.com/cloud-cross-project-releases
Are you trying to get only the list of all releases in the instance or use releases across multiple projects?
Hi @yuna ,
I might be late with my answer but I would like to suggest another alternative which can solve your problem.
We have created Release management add-on for Jira data centre and Jira cloud which helps to create cross-project versions in Jira. It also can help to synchronize versions between multiple projects and compose packages of multiple versions.
Out of the box, there are a few more handy features, such as:
Hope it will help you to automate daily release routines.