The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Splitting this from #2995626: RoadMap: 1.0 Release to track tasks required for completion and delivery of our initial publication and dev release of the project.
MVP User Stories
| Complete? | User Story | Implementation Ticket |
|---|---|---|
| User Permissions | ||
| Y | As a site administrator I may grant user roles permission to administer all switches. | #3009381: Permissions: Administer Switches |
| Status Overrides | ||
| Y | As a developer I may override and force the activation status of a configured Switch from settings.php. | #3009719: Make activationStatus override-able via config |
| Activation Status Conditions | ||
| Y | When checking the status of a non-existent or disabled Switch, the default activation status from Switch system settings is returned. | #3010151: Baseline Activation Condition Behavior |
| Y | When checking the status of a non-existent Switch a warning is logged. | #3010151: Baseline Activation Condition Behavior |
| Y | When checking the status of an existing Switch with no configured activation conditions the Switch is assumed to be inactive and returns false. | #3010151: Baseline Activation Condition Behavior |
| Y | When checking the status of an existing Switch with configured activation conditions all conditions are evaluated using AND logic. | #3010151: Baseline Activation Condition Behavior |
| Condition Configuration | ||
| Y | As a site builder, I may selectively enable and disable available condition plugins to be used on a condition-based switch. | #3012839: Conditional Switches may opt-in to condition plugin usage |
| Y | As a site builder editing a condition-based switch, I may not configure condition plugins that have not been marked as enabled within the enabled plugins tab. | #3012839: Conditional Switches may opt-in to condition plugin usage |
| Y | As a site builder using a condition-based switch, only condition plugins I have marked as enabled for a switch are used to determine the activation status of that switch. | #3012839: Conditional Switches may opt-in to condition plugin usage |
| Y | As a site builder editing a previously created condition-based switch, the configuration for all previously configured and enabled switches is maintained when I view the form again. | #3012839: Conditional Switches may opt-in to condition plugin usage |
| Y | As a site builder editing a previously created condition-based switch, the selection for available condition plugins to be enabled reflects the same selections from the last time the form was saved. | #3012839: Conditional Switches may opt-in to condition plugin usage |
| Y | As a site builder editing a previously created condition-based switch, any prior configuration for a condition plugin is not maintained when viewing the form again after saving the switch with that plugin marked as disabled. | #3012839: Conditional Switches may opt-in to condition plugin usage |
| Theme Layer Integration | ||
| Y | As a developer varying output within a Twig file, I may conveniently reference the activation status of a Switch within Twig. | #2998566: Create a Twig extension to check flag values |
Comments
Comment #2
sluceroComment #3
sluceroComment #4
sluceroComment #5
sluceroComment #6
sluceroComment #7
sluceroEach of the related tickets listed below have all had their work merged into the
8.x-1.xbranch, so the codebase is ready for a dev release to be created.Comment #8
sluceroThis initial dev release has been completed and created: https://www.drupal.org/project/switches/releases/8.x-1.x-dev