Archived toggles are always displayed as active
Nezz opened this issue · 0 comments
Nezz commented
Describe the bug
When a feature toggle is archived, it is always displayed as active:
Steps to reproduce the bug
- Create a feature toggle that is disabled in all environments:
![Screenshot 2023-07-21 at 17 24 15](https://private-user-images.githubusercontent.com/431167/255202785-bde8fced-693b-4c2e-b50c-0e7240b1c507.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDQwNDc2OTIsIm5iZiI6MTcwNDA0NzM5MiwicGF0aCI6Ii80MzExNjcvMjU1MjAyNzg1LWJkZThmY2VkLTY5M2ItNGMyZS1iNTBjLTBlNzI0MGIxYzUwNy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjMxMjMxJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDIzMTIzMVQxODI5NTJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1lZDBjMTYyZDhjYTc4NThlOGQ3ZGU2OWZiNmYwMDZlZDBjNTBhNDAzZGM2ZmJiMDVmYTE5ODc3NDc5YzY0OTgxJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.uV8ide4o52MNfzwavdEML0pTvrp7-i22qxNFRa4DXSQ)
Expected behavior
The project archive has a "State" column which has the value "Active" for all the feature toggles we have archived over the years. This is highly confusing because the feature toggles are actually inactive once archived.
Possible solutions:
- Drop the state column
- Hardcode the state column to "Inactive"
I was told that "What you're seeing in the UI is the state the toggle will get if revived". This however is confusing to our employees. If it is really meant to show that then it should be phrased that way and updated to support environments.
Logs, error output, etc.
No response
Screenshots
No response
Additional context
No response
Unleash version
5.2.8
Subscription type
Enterprise
Hosting type
Hosted by Unleash
SDK information (language and version)
No response