Improve Auto DevOps settings flow for admin and project
Problem
Currently, within project/admin settings, we include a section for Auto DevOps settings. Here a user can enable or disable Auto DevOps. The idea of "enabling Auto DevOps" as a whole is incorrect and confusing because there are multiple aspects to Auto DevOps that need to be configured in order to work properly.
Using the verbiage "Enable Auto DevOps" within project settings gives users the expectation that all they need to do is click enable and save. This problem was validated in our user research: ux-research#67 (closed). In this study, most users were unfamiliar with Auto Review and Auto Deploy and many were confused about whether those features were part of Auto DevOps. Most users were unsure what a domain was for and all users were not aware they needed a cluster (to be further addressed in [ADD ISSUE NUMBER].
Problem Statement
"Enabling" Auto DevOps really means defaulting to the Auto DevOps pipeline when no other configuration file is found. This should be clear to users so that users do not have the expectation that Auto DevOps will work just by enabling.
Proposal
- Update copy for Auto DevOps pipeline setting with admin area and project settings
- Reduce complexity by making the setting a checkbox, rather than three radio buttons
Admin area
Disabled | Enabled |
---|---|
Project settings
Disabled | Enabled | Instance enabled |
---|---|---|