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!


What's the best approach when rolling back a version in Jira?

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:

  1. Unreleased
  2. Released
  3. Archived

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?  

1 answer

0 votes
Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 22, 2023

Hi @Connor Skiro 

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.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events