docs: features that became standard, and Feature Flags moving up the settings menu - #15678
Open
devGregA wants to merge 1 commit into
Open
docs: features that became standard, and Feature Flags moving up the settings menu#15678devGregA wants to merge 1 commit into
devGregA wants to merge 1 commit into
Conversation
…settings menu Nine optional features are now on for every instance and no longer listed on the Feature Flags page, so the page needed to explain what it means for a feature to leave that list. The FAQ said upgrading never changes your settings. That is no longer true for a feature promoted in the same release: its stored setting is cleared, because an instance that had opted out would otherwise stay off with no toggle left to change it back. Answered directly rather than left as a surprise. Connector Requests is no longer shown as "Unavailable on This Deployment" on-premise -- it is off the page entirely -- so its availability row says so. Threat Modeling is on by default and switchable by a superuser, rather than enabled per instance on request, and Feature Flags now sits above the settings groups instead of inside System. English only; the de/es/fr/ja translations regenerate from these pages through the pipeline in docs/TRANSLATIONS.md.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Documentation for the feature-flag changes shipping in the same release: nine optional features become standard and leave the Feature Flags page, five more default on, and the Feature Flags entry moves up a level in the settings menu.
Three pages change.
admin/feature_flags/PRO__feature_flags.mdnavigation/PRO__settings_menu.md— Feature Flags is no longer inside the System group. It sits above the groups, directly under All Settings, and is still filed under System in the All Settings directory. The group table and the "what moved" table both follow.sensei/threat_modeling.md— threat modeling is on by default and a superuser can switch it off or back on from the Feature Flags page, rather than being enabled per instance on request during beta. It stays labeled BETA, and the Sensei entitlement is unchanged.English only. The de/es/fr/ja translations are regenerated from the English source through the pipeline described in
docs/TRANSLATIONS.mdrather than hand-edited.