How do you document a rollback?

[major li]

Hi community,

Good day.

How do you document the rollback if it happens? It is known that if we want to implement a new feature, we will use story to capture it. But if the same feature need to rollback, how do you manage it to keep data quality? It will really help the troubleshooting in the future. 

Thank you. 

[Anand Kumar P · Accepted solution]

Hi @major li ,

Create a separate rollback story, link it to the original completed story, and document the rollback in work notes, don’t reopen the original story.

If my response helped, please mark it as the accepted solution ✅ and give a thumbs up👍.
Thanks,
Anand

[Dr Atul G- LNG]

Hi @major li 

As a BPC, and having also worked as a Change Manager and Release Manager in my previous roles, rollback has always been a critical aspect for me. Rollback generally has two sides:

• A rollback that works on paper

• A rollback that requires actual physical effort to be carried out

Whenever a rollback scenario comes into a project, the first thing to evaluate is whether the functionality can be hidden instead of performing a full rollback, or whether the rollback itself might introduce additional issues. In many cases, rather than rolling back completely, we can add a new feature that isn’t 100% visible and control its access using ACLs to hide the functionality.

Recommended approach:

• Create a new story and use the prefix “Rollback”.

• Create the required change for the same and get it approved.

• Before executing a rollback, ensure it is thoroughly tested in the lower or development environments first.

These are the key points you can consider, mate.

[Dr Atul G- LNG]

Hi @major li 

Hope my answer provides you a good way to move forward.