You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our team has 2 use cases where being able to set Feature Flag values in a more streamlined way is desired. For us, the most preferred method would be via URL query params.
For example, /dashboard?new-account-billing=true might force a boolean feature flag new-account-billing to true.
While our development team uses the extension, the requirement to use an API token means it's not suitable for our non-technical team members.
Our most common use case for this is QA'ing new features with our product and marketing teams, who are not technical. A common problem we have is that they don't understand how to toggle the features via the Growthbook dashboard, which slows down our QA process and forces developers to get involved to help it along.
A secondary use case, but one we've run into a handful of times, is opting specific customers into a feature flag value. Occasionally we'll have a customer notify us of a bug, and we'll opt them into a beta feature that is feature flagged to see if it resolves it for them. We've had to do this via forced rules tied to their ID in the past, but this isn't very customer support friendly, and leads to forced rules hanging around longer than they're needed.
Please let me know if there's any additional information that I can provide. Thanks!
The text was updated successfully, but these errors were encountered:
Description of Feature
Our team has 2 use cases where being able to set Feature Flag values in a more streamlined way is desired. For us, the most preferred method would be via URL query params.
For example,
/dashboard?new-account-billing=true
might force a boolean feature flagnew-account-billing
to true.While our development team uses the extension, the requirement to use an API token means it's not suitable for our non-technical team members.
Our most common use case for this is QA'ing new features with our product and marketing teams, who are not technical. A common problem we have is that they don't understand how to toggle the features via the Growthbook dashboard, which slows down our QA process and forces developers to get involved to help it along.
A secondary use case, but one we've run into a handful of times, is opting specific customers into a feature flag value. Occasionally we'll have a customer notify us of a bug, and we'll opt them into a beta feature that is feature flagged to see if it resolves it for them. We've had to do this via forced rules tied to their ID in the past, but this isn't very customer support friendly, and leads to forced rules hanging around longer than they're needed.
Please let me know if there's any additional information that I can provide. Thanks!
The text was updated successfully, but these errors were encountered: