Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 51,013
    • Issues 51,013
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,561
    • Merge requests 1,561
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #364700
Closed
Open
Issue created Jun 08, 2022 by Rayana Verissimo@rayana💬Developer

Link to deployment commit from the Environments page

Insight

Users go to the Environments page to check how their deployments are doing -- for example, troubleshoot a failed deployment, see the last successful deployment and rollback, share that information with their teams, and identify dependancies. Because that information is missing or is difficult to find, some participants navigate to the Pipelines page instead to see a complete list of previous deployments and their commits for an environment.

Today, users can copy a SHA but cannot click to go and check the information about the commit pipeline.

Users can see the link to the pipeline commit in the UI, but that text is usually a generic text that reads Merge branch abcd into efgh`... and is not relevant to them if the deployment is always pointing to production.

Supporting evidence

None of this is links, I think is it used to be, I mean, the commit should obviously be a link

Again, quickly navigate not having to search for stuff. It's I know it's I know it's there. I want to quickly know what was in that commit. Oh yeah. I want a good site commit and then compare to previous type of previous version or something quickly Because I always go, I'm often on this page. It's pretty much always open on my computer. I ever really used it at all. Even though we don't have that many environments, I do use it all.

This is what I expect to see which the problem, when, which branch, which commit, who deployed it

I use that page to see a development has the new dashboard on it. And it's that commit deployed at that time. That's what I'm interested in basically.

Action

  • Make the commit SHA link to the commit page for a particular deployment.

Resources

  • 🕊 Dovetail project
  • 🔍 Research issue

Tasks

  • Assign this issue to the appropriate Product Manager, Product Designer, or UX Researcher.
  • Add the appropriate Group (such as ~"group::source code") label to the issue. This helps identify and track actionable insights at the group level.
  • Link this issue back to the original research issue in the GitLab UX Research project and the Dovetail project.
  • Adjust confidentiality of this issue if applicable
Edited Aug 11, 2022 by Rayana Verissimo
Assignee
Assign to
Time tracking