-
New Feature
-
Resolution: Fixed
-
Minor
-
None
-
-
2.395
The idea is to let users enable/disable features in Jenkins.
That will drastically help proposing new features without breaking the ecosystem, like new design for a page, new behavior, etc.
Using the same system, we could also propose customization of some behavior, per users.
After an initial version, we will be able to add some telemetry on top of that, to better understand the adoption of some features, and better define priorities / initiative to abandon, etc.
With this approach, big UI change / revamp can be hidden behind a flag, reducing the need to a full agreement before merging a PR.
- relates to
-
JENKINS-69869 Categorize the user properties
- Resolved
- links to
Two good candidates that I have in mind at the moment:Enable/disable of the "new" Jenkins header That feature was removed jenkins.io/pull/5595Defining the timer for the auto-refreshable widgets on the side panel (perhaps only interesting for developpers working with JS, not sure)Interesting / ironical usage: The split of user properties into categories could be such feature flag, to let people continue using the previous approach