Create a runner read-only view in the admin area
Runners in the admin view have a distinctly different details view than those in the project and group views. To provide users with the most valuable information about runners, and to improve the consistency of our runner details, a read-only view of runners should be used in the admin view, and eventually for the project and group views.
Problem to solve
Runners in the admin view have a distinctly different details view than those in the project and group views. This is especially confusing when you are jumping from each view as an admin. They are also missing out on important metadata about that runner when only in the admin view, as we don't print out the same details that we do when you are in a project or group.
Track the number of visits to read-only views of runners (clicks on the runner name links)
User experience goal
Have a single consistent experience to view details of a runner across the product, starting with the admin area.
Create a new read-only view that appears when you select a runner name (link) from the runner admin table.
🎨See design management designs below
✨Figma design file Warning: This file is huge so it may be difficult to navigate. I'd suggest checking out the prototype for final interactions.
Eventually, we will be able to reuse this read-only view for developers who do not have access to edit runners. We'll have to do some permission checks to ensure they are able to see the appropriate metadata, but it will open the door for developers to understand more about runners if they ran into a problem.
Extra basic details (executor, architecture, platform)
Jobs tab paginated (!80380 (merged))
Assigned Group (!78680 (merged))
Assigned Projects paginated (!79239 (merged))
Assigned Projects filtered
Pause/Resume button (!78483 (merged))
Permissions and Security
Administrator capabilities for self-managed
Availability & Testing
What does success look like, and how can we measure that?
Success would be that administrators are able to solve their runner problems faster by finding the appropriate metadata faster. We'd have to compare the current experience to the new one to effectively measure that.
What is the type of buyer?
Is this a cross-stage feature?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.