Skip to content
Snippets Groups Projects

Improve the admin runner table design to make use of new list design standards

    • Closed Issue created by Gina Doyle @gdoyle

    Problem

    Data is not currently readable in all viewports within the admin area runners table. The columns quickly collapse and data becomes overlapped. Not all of the data shown in the columns are equally important, but are treated that way. We want to add more data to the table (like an owner and creator of runners), and that is not possible in the current table format. This acts as an additional follow-on to #340324 (closed). The goal is to use the outcomes of #340029 (closed) to apply new list view design standards to the runner tables.

    JTBD: When I am managing the execution of many CI jobs, I want an overall understanding of the job execution agents connected to my organization, so I can make effective decisions.

    User experience goal

    The goal of this additional redesign is to improve consistency throughout our table/list views and increase the flexibility of adding more data to the table, as well as improving the readability of that data.

    Proposal

    These changes should be developed behind a frontend-only feature flag. We should enable this for gitlab.com first and gather feedback. We can then make any iterations necessary before enabling for all users.

    :sparkles: Designs in design management

    :art: Figma

    UX Definition of Done

    :one: VALIDATION TRACK

    Problem Validation Phase

    • Problem is well understood and has been validated
    • JTBD is well understood and has been validated
    • PM has communicated the opportunity canvas to stable counterparts and group stakeholders, including the Product Designer and Product Design Manager

    Design Phase

    • Document the JTBD and UX goal in the issue/epic description
    • Explore multiple different approaches as a team
    • Discuss the technical implications with Engineering
      • Identify any potential cross-team dependencies and include the DRIs in the discussions
    • :bangbang:️ Blocker to getting this into workflowready for development Identify a small set of options to validate
      • Document the user story(ies) for the MVC
      • Consider edge cases for each user story
      • Create prototypes or mockups for each user story
    • Pajamas component lifecyle
      • Identify component design or pattern update/creation
      • Discuss the technical implications with Engineering
      • Pajamas issue is created (within the scope of the MVC)
    • Update issues/epic descriptions
    • Proposed solution(s) identified and documented in the issue/epic description

    Solution Validation Phase

    • Validate the solution to increase confidence in the proposed solution
    • Document the solution validation learnings
    • Product Designer has communicated the solution validation learnings to stable counterparts and group stakeholders, including the Product Design Manager
    • Update the MVC proposal with relevant insights from the solution validation
      • Discuss the technical implications with Engineering
      • Update issue/epic description to contain or link to the findings

    :two: BUILD TRACK

    Plan Phase

    • Proposal is ready to be broken down and prioritized by PM for development

    Develop & Test Phase

    • Product Designer reviewed MRs that include user-facing changes, as per the Code Review Guidelines
      • UX Debt issues have been identified and assigned to a milestone
    24 of 28 checklist items completed · Edited by Gina Doyle
    Loading
    100%

    Child items ...

    • Activity

    Please register or sign in to reply