- Customers view how they are using GitLab from a feature perspective.
- View how they compare with other organizations, and see how far they are away from a better metric.
- Discover features that they are not already using, or using incompletely.
- Learn about best practices by visiting relevant blog posts and white papers.
- Self-service inside their GitLab instance.
- Sales team views exactly same information as the customer, for ongoing relationship management and sales opportunities.
- When conversing with customers, refer to same exact view so easily have a coherent conversation.
- View from within
version.gitlab.comand know that it is the same view as customer's (who is viewing it from their GitLab instance.) https://dev.gitlab.org/gitlab/version-gitlab-com/issues/55
Scope for this issue
View is only accessible if the instance has usage ping configured on.
Only instance admin has access to the view.
- View how many objects created in last 30 days of data for a given metric.
- The metrics are calculated on
version.gitlab.comand returned back to the customer's GitLab instance to display. Details at: https://dev.gitlab.org/gitlab/version-gitlab-com/issues/56.
- This includes individual metrics.
- This includes the aggregate Conversational Development Index.
- Colors apply to the individual metrics (the boxes), and also the convdev index score itself, and the I2P icons.
- [0, 33.33): Red
- [33.33, 66.66): Orange
Top information appears on first visit until the user dismisses it:
View without top information:
Hovering over an item in the bottom timeline graphic expands the graphic to show I2P stage name. The color of the icon reflects the average of the features it relates to, per the color scheme above, and the averages per:
- Idea - issues
- Issue - average of issues and comments
- Plan - average of milestones and boards
- Code - merge requests
- Commit - merge requests
- Test - pipelines
- Review - average of pipelines and environments
- Staging - average of environments and deployments
- Production - deployments
- Feedback - average of monitoring and service desk
Timeline graphic will only appear on larger screens. Columns will wrap at smaller screen sizes and so the timeline graphic would no longer equate to the features correctly.
Empty state: Usage ping not enabled
Empty state: No data yet
Top info graphic: illustration-convdev.svg
Empty state svgs:
Documentation and blog post / article / white paper links
|Doc||Blog post / article / white paper|
|Issues||Digital collaboration by Deloitte|
|Comments||Why conversational development?|
|Milestones||Link||ConvDev Principle 1: Shorten the conversation cycle|
|Boards||Link||User Story Mapping by Jeff Patton|
|Merge requests||Link||The Humble Craftsman by Uncle Bob|
|Pipelines||Link||Continuous Delivery by Martin Fowler|
|Environments||Link||GitLab CI: Deployment & Environments|
|Deployments||Continuous Delivery Vs. Continuous Deployment: What's the Diff? by Puppet|
|Monitored projects coverage||Link||Prometheus Overview|
|Service desk issues||Link||Top Trends for Customer Service by Forrester|
- Metrics are calculated on version.gitlab.com server - instance score, leader score, level (low, medium, high)
- Metrics are transferred as the response to usage ping
- Metrics are saved in the database of the GitLab instance
- Rendering the ConvDev Index page doesn't cause any additional requests to version.gitlab.com