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

How to manage multiple products in one release

Martijn Schuurmans
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 21, 2023

With out team we are working on a cloud sllution, embedded software on a IOT device, local software runing on a server and a mobile app. These products work closely together so in a release we need to synchronise the different software versions. How can I manage that in Jira?

1 answer

0 votes
Jens Schumacher - Released_so
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 21, 2023 • edited
If you are referring to the challenge of creating the same version in multiple projects, this has been covered in a few posts already. You can find one answer here.

To summarise: It is possible to synchronise the creation of release versions in Jira using Jira Automation. 

For creation:
  • Trigger: When a new version is created.
  • Action: Create the corresponding version in the other project.
  • Action: Set the entity property.
  • It is advisable to use an entity property in the project to store the relationship between the two versions. This way, you can easily identify which version needs to be updated in the future. If you have a better alternative, you are welcome to use it.

For updating:
  • Trigger: When a version is updated.
  • Action: Read the project property, possibly by sending a web request to the project property endpoint.
  • Action: Update the version, possibly by sending another web request to the version endpoint.
There are also a number of third party apps that handle the syncing for you:


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events