I just got access to our company's growthBook earlier today and was playing around with it a bit to get to know the ins and outs and discovered something which I think is strange. Specifically when you delete a feature and then create a new feature with the same name. History and versioning seems a bit messed up.
See below some steps to reproduce:
1. create a feature
2. make some changes resulting in 2 new versions to be created (version 2 and 3)
3. delete the feature
4. create a new feature with the same name
expected behaviour (option a):
• a new feature is created without any trace of the old feature's history
expected behaviour (option b):
• a new version of the old feature is created with the trace of the history and the current version is version 4 (or 5 if you consider the deletion being version 4)
• a feature is created with version number 1 (but versions 2 and 3 of the old feature are accessible, as well as the audit log)
• if you create a new version, this will be version 2 (the draft will be shown next to the existing version 2), will this overwrite the original version 2, will there be 2 version 2's, or will the system crash, unsure (and I'm not intending to test this out 🙂)
I doubt that this is expected behavior, but since I only played around with the tool for an hour or so, my knowledge in the tool is still limited. Could you please advice? Is this expected or actually a bug? Do I report this in github, or do you take over from here?
note that the screenshot here mentions "Reverting to version #2" but this is not the reason for mainaining version 2. If I abort the change and do a different change, it will also suggest version 2