Project license compliance empty states
NOTE if you are a user who also would like to see this feature, please UPVOTE
Problem to solve
When license scanning is not enabled, the empty state if the sections UI is not explicit that is the case. Additionally, the sections sub-navigation items are not shown (when scanning is not enabled): detected in project and policies
empty state UI
When I using a security scan for the first time, I want to know how to set it up, so that the security team can start using them for GitLab projects.
As a developer, I want to see licenses detected in the projects and policies, so I can ensure the project is in compliance.
Intended users
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sam (Security Analyst)
Further details
Supports ongoing improvements to empty state UX: #200003 (closed)
Proposal
- Display warning banner when configuration is not complete, allow user to add policies in either state (so policies may be added and effective once configuration is complete)
- Make explicit in the UI why results are not shown (bc scanning hasn't been enabled)
- Guide user to documentation and/or make setup instructions explicit in UI
- Show
detected in projectandpoliciestab for user awareness of UI feature
Permissions and Security
...
Documentation
What does success look like, and how can we measure that?
Upon landing on the empty state:
- Does the user understand why the feature isn't yet working?
- Does the user understand how and/or next steps to use feature?