I don't quite understand why this isn't allowed? What if I want to have two in the "off" state and one on the "on" state? I have two feature keys using the same experiment key to coordinate behaviour in two places for the same experiment

Hey James - I'm not sure I understand your use case 100%, but in regards to your question about why you can't have more than 2 variations - it looks like you've selected a

boolean

type flag - which inherently only provides two possible values -

on

and

off

. Selecting a different feature flag type (

json

,

number

, or

string

) does give you the option to add more than 2 variations. Given your use case, rather than creating two feature keys using the same experiment key to coordinate behaviour, is there a reason you couldn't check the same feature twice in the two different places?

Not really possible in our use case

@busy-horse-73824, my guess is we designed it this way initially to avoid confusion for users, but I definitely see your point that allowing experimenters to have multiple groups with the same boolean flag makes sense. Of course, a work around is to use a different flag type for now. However, the longer term solution that we are working actively on having an experiment serve as the source-of-truth for variations. In this case, you could explicitly link multiple features to the same experiment, and in this process we'd need to handle the case where multiple variations got a

True

or

False

value for a boolean flag. (cc @future-teacher-7046)

Ah that does seem like a much better way around, in terms of data model. I currently do quite a lot of teaching around how to run more advanced/coordinated A/B tests like this one, but that would make it much simpler I think