Validate UI messaging on License and Dependency list
What’s this issue all about?
This issue focuses on https://gitlab.com/gitlab-org/gitlab-ee/issues/13582 and https://gitlab.com/gitlab-org/gitlab-ee/issues/12190 (related: https://gitlab.com/gitlab-org/gitlab-ee/issues/13298). Specifically, the messaging with the header (with ?
icon linked to documentation), subtext (aiming to clarify UI content), and anchor to the pipeline (with the corresponding timestamp of latest succeed). This messaging pattern aims to proactively inform the user about the UI content and how/when the data is displayed.
Planning to research this issue concurrently with #359 (closed), leveraging the same study and participants for feedback. (prototype, the compliance list and dependency list task will be at the end of the #359 (closed) flow user task)
Who is the target user of the feature?
- Developer
- Lead developer
- Compliance officer
What questions are you trying to answer?
- Does the user navigate to easily to the Compliance List and Depencey list nav link? (when given task)
- What is the user general perception of each page?
- Can the user articulate when/where the info displayed comes from / is updated?
- If the user is unsure or has questions - what do they do? Is the
?
considered or noticed in this case? - What does the user think
?
is? If they think it’s a link, where do they expect it takes them? - When the user lands on the page, do they know where they are at?
- What are the user expectations with “License Compliance”?
- Is it clear the data is from the default branch?
Core questions
- Can the user navigate to the dependency list and compliance list with ease?
- Does the user understand the data and where/when it comes from?
Additional questions
- What would be helpful that may not be visible and/or a feature we have?
- How do they think about license/dependencies?
- What, if any, is there current compliance workflow needs?
What hypotheses and/or assumptions do you have?
- Our test participants have a general understanding of what dependencies are in terms of the development process; but some may or may not deal with compliance related issues
- Hypothesis is that the subtext, pipeline link, timestamp, and
?
will be a helpful improvement to proactively message to the user what the page is and how/when it’s updated. Versus, the UI reactively showing error messages when it “may be out of date”. The user would have their own definition or “out of date”, and the timestamp will help them identify as such.
What decisions will you make based on the research findings?
- Improve the copy used in the subtext
-
?
icon link to documentation, or consider using text (such as “Learn more”) - Continue using the pattern for other Secure feature
- Propose usage of pattern in design library
Links: