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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Great to be a part of this community.
Had some queries on the best practices for release management.
We follow a micro service architecture with around 16 services each having their own fixversions in JIRA. They are interconnected and have dependencies.
A single release can have a few of the 16 services. It gets really difficult tracking the versions going on a release day.
In this case how do I manage this Group Release in JIRA?
Temporary solution - I have added a prefix before each fixverion to identify it.
for eg. (5)ATL-21, (5)LEG-21 .. where (5) denoted the group release.