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.
We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events