Epic: Implement Flag Versioning in the API and UI

[dabeeeenster]

We are already doing some versioning of Flags for Change Requests. We could build on this and keep a history of all flag state changes. This would allow users to roll back to previous states, view state history etc.

This could also tie in with the Audit Log - allow you to link fro the Audit Log to a specific flag version.

Suggest having a "Version" tab in the flag modal that shows you all the versions of the flag as well as their state changes.

Note!

• Engine for versioning is in Open Source
• Flag versioning view/roll back and alerting for stale flags is in Scale up and Enterprise

[matthewelwell]

@kyle-ssg the API is now ready for change requests to include versions. The plan, as such, is for you to create the version (or versions), then attach those to the change request. See docs for creating a change request with a version here:

Edit: again, this is only currently available in staging.

[flagsmith]

Flagsmith feature linked: feature_versioning
Default Values:

Environment	Enabled	Value	Last Updated (UTC)
Production	❌ Disabled		2023-08-10 13:04:20

Segment flagsmith_team values:

Environment	Enabled	Value	Last Updated (UTC)
Production	✅ Enabled		2024-02-01 10:36:43
Staging	✅ Enabled		2023-08-10 13:04:28
Demo	❌ Disabled		2023-08-10 13:04:20
Demo	✅ Enabled		2024-02-15 12:48:20
Self hosted defaults	❌ Disabled		2023-08-10 13:04:20
Live	❌ Disabled		2024-07-03 16:56:25
Live	✅ Enabled		2024-07-03 16:56:26