Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Category Direction - Feature Flags

Feature Flags

Feature Flags can be used as part of software development to enable a feature to be tested even before it is completed and ready for release. A feature flag is used to enable or disable the feature during run time. The unfinished features are hidden (toggled) so they do not appear in the user interface. Tying into our progressive delivery strategy, this allows many small incremental versions of software to be delivered without the cost of constant branching and merging.

Feature flags unlock faster, more agile delivery workflows by providing flexible control over deployments to a specific environment or audience. In addition it reduces risk to production. In case a problem is detected, disabling the feature is as easy as turning off a switch.

Feature Flags is built with an Unleash-compatible API, ensuring interoperability with any other compatible tooling, and taking advantage of the various client libraries available for Unleash. Unleash have recently announced that they are spinning up a hosted (paid) option while maintaining their open source offering. We will be monitoring this closely.

While Feature flags are a great tool for incremental delivery, they also introduce technical debt, sometimes feature flags are forgotten and left as stale code. In order to overcome this challenge we plan to notify users when the time comes to expire a feature flag gitlab#8527.

What's Next & Why

We have released Feature Flags supporting % rollout (gitlab#8240) and userID (gitlab#11459) strategies. However, our current solution has several limitations, the most important one, is restriction of setting a single feature flag strategy to all environments. We are now working on unlocking this limitation and improving the user experience associated with it by adding the ability to support multiple strategies per environment via API with gitlab#204895 and via the UI with gitlab#35555.

To make working with userIDs easier, we plan to introduce the list strategy, which will allow you to store userIDs in lists that can be reused across multiple feature flags. This will be accomplished via API support in gitlab#205409 and UI in gitlab#13308.

We are interested in learning more about your Feature Flags use cases and needs and invite you to participate in our user research, please register or respond to our survey.

Maturity Plan

This category is currently at the "Viable" maturity level, and our next maturity target is Complete (see our definitions of maturity levels).

Our focus at the moment is on using the feature internally to deliver GitLab itself. This is driving new requirements to the base features that are out there, and also helping us to ensure the list for complete maturity is accurate. Our plan is for our feature flag solution to compete with other products on the market such as LaunchDarkly or Rollout. As we work towards complete maturity, our expectation is that our primary adopters of this feature will be pre-existing GitLab users looking for incremental value. For buyers who are considering replacing JIRA, and looking for something that integrates feature flags with issues, we can also provide a valuable solution as we head towards complete maturity.

Key deliverables to achieve this are:

If you are interested in understanding the roadmap in a more granular fashion, you are welcome to follow these epics:

Competitive Landscape

Other feature flag products offer more comprehensive targeting and configuration. The simplicity of our solution is actually a strength compared to this in some cases, but there is some basic functionality still to add. As we are rigorously working to close the gaps with the competitors, our next strategy to tackle will be the ability to configure feature flags based on groups gitlab-ee#13308

There is a detailed LaunchDarkly comparison from when the project was first being conceived here.

We are conducting a renewed competitor review of LaunchDarkly in gitlab#197727. If you have additional insights or are interested in joining in the conversation, please comment on the issue.

Analyst Landscape

Analysts are recognizing that this sort of capability is becoming more a part of what's fundamentally needed for a continuous delivery platform, in order to minimize blast radius from changes. Often, solutions in this space are complex and hard to get up and running with, and they are not typically bundled or well integrated with CD solutions.

This backs up our desire to not over complicated the solution space here, and highlights the need for guidance. gitlab#9450 introduces new in-product documentation to help development and operations teams learn how to successfully adopt feature flags.

Top Customer Success/Sales Issue(s)

Since GitLab serves as a single application tool, users who use our feature flags and issue management, can associate feature flags directly from the issue and vice versa and view the current deployment status via (gitlab#26456).

This will provide visibility from the issue itself, and will let you know which feature flag is associated with it, its status, and percent rollout from the feature flag view, enabling you control and insights from wherever you wish to manage your feature flags.

Top Customer Issue(s)

Top Internal Customer Issue(s)

Delivery Team

Top Vision Item(s)

One of our main themes in CI/CD is Progressive delivery. Feature flags, by definition is a form of progressive delivery as it allows you to deploy code incrementally and control the audience that will receive the new code.

Our top vision item is to allow simple monitoring and management of the feature flags in the system, which can become a complex take once there are many feature flags in place. A feature flag dashboard as described in gitlab#2236 will make this an easy task.