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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Create Release across multiple projects

Currently we are having more than 10 projects that teams are using for their respective sprints task. 

I want to create single release for the following projects - FEED, AT, SPST, FUL out of my all projects. Is there a way to achieve the same, instead of using separate releases for these projects?



1 answer

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 02, 2021

Hi @Dhruv Singh 

This is not possible to do today within Jira Software Cloud.  A release or version is bound within the scope of that particular project.  We do have a feature request that seeks to share a release among multiple projects over in JSWCLOUD-16637.

That said, if you were using Jira Advanced Roadmaps found in the premium Jira Software Cloud subscription, then you could use a cross-project release as mentioned in Create a cross-project release in Advanced Roadmaps.  But it's not clear to me if this would be helpful to your specific use case here, that article does mention that this cross-project release doesn't add any data to the issues themselves, and instead is only used to help align multiple single project releases.

I hope this helps.


Fernando Eugênio da Silva
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 25, 2022

I managed to develop a way to create these releases in several projects at once.

See how:

You will need to create a phantom issue on each project just to be responsible for project allocation and visibility within the automation. In this case and to help, I created a small automation that makes clones of my issue in each project where the release will be created.

But issues can be created manually.
- Create the issue in each project with a subjective name so that nobody deletes it;
- Choose one of the issues to be a kind of parent issue and associate all the others to it by a type of link, in this case I chose "Relates to"

Creating automation:

Choose the trigger: SCHEDULE and put it to run 1 time a month (just to guarantee the next step);

In the JQL, enter the issue you chose to be the PARENT and place. In my case, it was the SUB-59.


Then add a "Create version" action to the automation and name it whatever you want.

Then add a branch, and choose for "Linked Issues", select the link type where you linked all child issues to the parent issue, in my case it was "Relates to".


After that, add the create release action again.

Put the same name and information that was entered in the previous action and you're done.

An important detail when selecting the release within the branch is to keep the "Current project" information in "Project".


Jira will read each issue related to the parent (branch) as a project, because they are issues from different projects.


After that, just give a "Run rule" in the schedule, see the results:


Then, just deactivate the automation and whenever they need to create versions in multiple projects, change the release information in each "Action" > Save the automation > Activate again and apply the "Run rule".


Hope this helps. Hahahaha

Like Andre Alforque likes this
Fernando Eugênio da Silva
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 25, 2022

Using the MANUAL trigger:

The automation only works sometimes, it seems that Jira is not able to read the branch when I change the trigger to MANUAL.

I opened another support ticket with atlassian to know more details.

But with the schedule it seems to work perfectly fine.

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 25, 2023 • edited

Hi - Thanks for the info.  I did get this to work BUT it only updates one of the Issues that I have 'Relates to' the parent.   I have 12 that need to be added.   Thoughts?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events