Solution validation: Commit history and display
What’s this issue all about?
Solution validation to combine investigation of these two issues
- Commit number not correct (gitlab#365327 - closed)
- Inconsistent Git history actions in views (remo... (gitlab#365729 - closed)
Who is the target user of the feature?
What questions are you trying to answer?
- Will users understand that "Commits" means "History"?
- When displaying the list of commits for a repository, how useful is the number of commits?
- Do users look at the number or do they view the list another way?
Core questions
Additional questions
What hypotheses and/or assumptions do you have?
- Assumption that users do not need the count of commits therefore hiding it would not be an issue.
- If this assumption is correct then rather than counting the number of commits, users would estimate the count
- We will test this by asking them which day had the most number of commits in a list of commits
- Hypothesis that changing "History" to "Commits" would not impact users to get to Commits
- We will ask the question in the language of "commit history" and see what users search for
- One task from the Project Overview, we would want to see users click on the link
{#} commits - One task from the Repository > Files page, we would want to see users click on the "Commits" button rather than the sidebar.
What decisions will you make based on the research findings?
What's the latest milestone that the research will still be useful to you?
Insights
- Renaming to button label to "Commits" aligned with participants thoughts when navigating to commit history
- Clicking on Commits was a clear path for navigating to commit history
- Participants were able to determine the correct day with the most commits without the number count
-
Using a date range would be a good way to search for commits
- Actionable Add date filter to Commits (gitlab#382824)
- On Project Overview, two participants thought that Changelog would link to history of commits
Links
Edited by Michael Le