Skip to main content

Dependent Features

Availability

Dependent features were first introduced in Unleash 5.7 for Pro and Enterprise users.

Overview​

Dependent features allow to define a child feature flag that depends on a parent feature flag.
A feature flag can have only one parent dependency but multiple child flags can share the same parent. For a child flag to be activated, its parent dependency must be enabled.

Parent dependency criteria​

  • Project Association: Both parent and child flags should belong to the same project.
  • Single Level Dependency: The parent flag can’t have its own parent, ensuring a straightforward, single-level dependency.

Managing dependencies​

Adding​

Introduce dependencies either through the UI or API, also applicable when copying a child feature with an existing parent dependency.

A button for adding parent dependency.

Removing​

Eliminate them through the UI or API. Dependencies are also removed when archiving a child feature. A parent feature can’t be removed if it would leave a child feature orphaned. To remove both, batch archive them. If Unleash confirms no other child features are using the parent, archiving proceeds.

A button for deleting parent dependency.

Permissions​

The Update feature dependency project permission, auto-assigned to admin and project members, allows managing dependencies.

Metrics calculation​

Metrics are influenced solely by the evaluation of child features.

Client SDK Support​

To make use of dependent feature, you need to use a compatible client. Client SDK with variant support:

If you would like to give feedback on this feature, experience issues or have questions, please feel free to open an issue on GitHub.