Runner UX Vision: Part 1

Overview

We would like to document the Runner UX Vision for Enterprise Management so that we have something to refer to as we make small iterations to the ideal outcome. In order to do so, we need to start with a single area that we know needs to be improved throughout the Runner Enterprise Management epic.

This issue is specifically for the Enterprise Management search and filter vision. A summary of the problems we want to solve for in the end product includes:

• Find out more information about a CI job that is not running - is there something wrong with the runner?

  • Things that would be helpful to filter by:
    • Who registered it, who is maintaining it?
    • Filtering by a specific project or many projects
    • Filtering by the runner ID, which is exposed on the job list
    • Filtering by a specific group or many groups
  • Ways that we have to go about it today:
    • Tags? If they're set up diligently
    • Have to go into the job to figure out project information
    • IP address is an additional clue to track down the user who created the runner

• Export the runners list

  • Ability to export a list that includes groups and projects that the runners belong to, see the user who created them, who maintains them, and last activity date

• Automatically remove runners that are "stale"

  • Provide users with an alert BEFORE deletion happens to make sure that admins and/or group/project maintainers are aware their runners will be deleted, with a summary of which ones will be removed. This allows them to possibly make changes before that deletion date.

✅ Designs

Figma prototype

✅ Video walkthrough

https://www.youtube.com/watch?v=8nSos4pbMng

WIP Runner UX page and updated direction page

We should also consider creating a first pass at a new Runner UX page, which would be a place in the handbook to include this SSOT.