Hi GrowthBook team, I have a small feature request that would significantly improve our development workflow. We currently use three environments. We start developing tests in dev, run QA in staging, and finally launch experiments in production. At the moment, it’s quite tedious to ensure that a test is running only in the intended environments, especially when multiple feature flags are involved. To move a test between environments, we need to manually disable/enable the test rules one by one. It would be extremely helpful to have a single toggle in the test configuration to control in which environments the test is active. This would simplify moving a test through the dev → staging → production pipeline. As an alternative, if GrowthBook DevTools allowed activating tests that are still in draft (not running yet), we could run QA without having to start the test prematurely. That way, we could validate everything in staging before officially launching in production. Thanks for considering this request!

Good feedback regarding the environment controls within the Experiment (versus only at the feature flag rule level). You actually can test draft experiments (you do not need devtools for this). Just include draft experiments from your SDK Connection settings.

@shy-orange-61738 check this comment from Bryce

@happy-autumn-40938 Thanks for your response, I totally missed that option! The option only appears when either Visual Editor or URL Redirect experiments are enabled. We don’t use either of those, which is why I originally couldn’t find the option. Is that expected? However, even after enabling it and adding personal access token to Dev Tools, I don’t see the draft experiments in the Experiments list. 😕 Any idea what could be wrong?

Apologies I misunderstood your question, these are only for visual experiments or url redirects. If you need to gate normal experiments, you can use attribute targeting on the experiment and/or on the flag that embeds the experiment