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. 

[Ankur Bawiskar]

@major li 

sorry your question is not clear

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[major li]

hi @Ankur Bawiskar , for example, as a PO, I create a story to implement a change in the system. It is released in the next day and I mark the original story as complete. Then 1 week later, I want to rollback to the previous version and the mentioned story is no longer needed. 

Then how can I make sure that the rollback information is maintained and the previous story is updated as well? 

Is there a practise/process in place according to you experience?

[TejasSN_LogicX]

Hi @major li ,

Create a separate story or task for the rollback.

• Treat the rollback as a new piece of work related to the original story.

Document the rollback details clearly.

• Explain why the rollback was needed, when it happened, and what changes were reverted.

• Include the impacted tables, scripts, or update sets, and attach screenshots or logs if possible.

Use Update Set descriptions wisely.

• When you roll back, mention “Rollback of [feature name]” in the update set name and description.

• This helps identify rollback actions during audits or when migrating between instances.

Add comments in the original story.

• Add a short comment saying the feature was rolled back and include a link to the rollback story or change record.

Follow Change Management (if used).

• In production environments, rollbacks are often recorded under a Change Request.

[major li]

Hi @TejasSN_LogicX , is it a real case?