Hello GrowthBookies, I have a question which also shades into feedback potentially. When I am creating a Feature Flag that will become part of an Experiment, I create the same Experiment Rule in prod, staging, and dev, with me copying over the same rule to the three environments so that it can be properly QAed. But in order for the Feature Flag Experiment Rule to be active/operational in the staging and dev environments - which the devs need to QA the experiment - it seems I need to start/run the experiment. This didn't use to be the case in a previous version, as far as I remember. Is there something I am overlooking, or is this the way that we are supposed to proceed now with creating and testing Feature Flags that have Experiment Rules used for assignment?

Hi 👋 I'm investigating this, but do you have an idea when you noticed the change?

We updated our Growthbook deployment for the first time in over a year a few weeks ago, so I don't know when the "change" was introduced per se. But is this not something that is pretty easy to see/verify? It seems like a core aspect of how Experiment Rules in Feature Flags are currently implemented.

Thanks for that. There was a recent change to "Copy rule" and you may have found a bug. Are you able to share some screenshots of your, so I can get a better understanding of what's happening?

This is what I am referring to. The experiment has not been started so the rule is skipped, but we would want to QA it in dev and staging before we start the experiment; this is not possible as the assignment rule the devs need to QA it is not active. Was that clear?

Thanks for that! I forwarded the message to the engineering team to see if they have any additional insight.