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
I'm currently automating our release management workflow in Jira and have successfully mapped out the process for when a release is completed.
However, given that Jira's releases only allow you to mark a Fix Version as:
Given the constraints, it seems like archiving a release that rolls back seems pragmatic but I'm curious, what are other folks doing to capture rolled back releases?
I think it depends on the next action after the roll-back.
If the release is rolled back, and a new release is setup to replace it, I'd go with archiving.
If however the release is rolled back, and a bug is raised (assuming there's a reason for the roll-back), I'd consider putting it back to Unreleased - to show that post-fix, it'll be re-released.