GitLab UX Team, 23 Nov 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Runner Enterprise Management: Runner details read-only and edit view design feedback

Description

Gina (Product designer, Verify:Testing and Runner) walks through upcoming proposed changes to runner details. If you are interested in leaving feedback, please do so in the designs in design management https://gitlab.com/gitlab-org/gitlab/-/issues/299758/designs/Table.png or through comments in https://gitlab.com/gitlab-org/gitlab/-/issues/299758

A

Hey everyone. I wanted to go through this pretty large design issue that um I've gotten a lot of feedback on already, but I'm looking to just get feedback on some specific areas before I put this into solution, validation.

A

So, uh to give you some background context around what this is runners today in the admin area they have, they can be edited and they include a bunch of different details that can be like configured depending on how you want the runner to run the ways that we show that today, across groups across projects and across the admin area which would be for the whole instance, um is not consistent.

A

So we're trying to improve the consistency and the usability there so that we can use sort of like the same paradigms for each area, no matter where you are because usually you'll be jumping between like project and group and admin area. If you were somebody who has access to all those areas, so I'll jump into this. um The first thing that I'd like to point out is that today, when you come to this table in the admin area, if you select the runner id or this pencil button, you get the same edit view.

A

So the main things that I've differentiated here is a read-only view versus an edit view and the read-only view would be selected if you um come from here and then the edit view would be showing up only if you come from the edit pencil.

A

um The reason why I did that is because we can reuse the read-only view in in areas where it's a developer. That does not have access to edit the runner. So we could just reuse that.

A

So, if you did just come to the read-only view, one specific thing that I was looking for feedback around is where I can put this pause button.

A

um I think this was kind of like a late edition, because I realized that we have it on this table and often users will interact with the play and pause buttons, and at this point so I want to make sure it's still relevant and in context. When you come to the read-only version of this, so one one thing that would be great to have feedback on. uh I separated the details and jobs here, so jobs has its own tab because there can be a considerable amount of jobs.

A

um So that's what that was. So if you did select the pencil button from here, you could come to the edit view of this.

A

So what's a little strange is I made the edit view more of like a form so anything that you change here, then the save changes button would become primary and then you can select save changes, but I did not want to include the pause button as I was showing in the beginning here, because it wouldn't be like an immediate thing that you could get feedback on, because this form is something that you would make changes on and then select save changes and it would save it that way.

A

um So what I did instead is we have the same. Checkbox for active uh is what we call it and that will determine whether or not you want the runner to be paused. So if you have it selected, then that means that it's that that would be the same as having it say, play on the the runner table and then, if you have it unselected, it would be as if it was paused.

A

The other thing that I was looking to get feedback on is when you have a specific runner, they have to have an assigned project. At least one. You can have tons of projects in your organization um and theoretically, it could be a lot to scroll through. So today we show that through a table- and we include enable buttons in there- it just really does not go along with many of our pajamas patterns. So I wanted to use a similar functionality that we're doing for assignees here so like for assignees for issues.

A

If you select an assignee, it jumps ahead of the divider and puts it under this assignees section. I wanted to use a very similar way of doing that here. So all the assigned projects would live above this divider and then once you select another project to add, it will jump up, and if you deselect a project up top, it will go back down.

A

The reason why I did this is because usually people will come in here and know exactly what project they want to assign so that they they will use the search bar rather than having to like search through a table um which I think just takes up unnecessary amount of space and then the last thing I was looking for feedback around was this type drop down, um so the shared runners have. This.

A

Has this kind of strange feature which allows you to make it into a specific runner, and it only goes in this certain way that you start with a shared runner and then you can make it specific um we're looking actually to deprecate that feature in, however many releases, but we are still collecting feedback from users to see if that is okay to do.

A

But I need to keep this feature in here for the time being, so this would allow you to switch the type to specific and then I've added this danger alert just saying that when you change this, you cannot change it back to shared like it will be specific runner forever. You would have to create a new shared runner to be able to get it to be shared, and then I did include this error alert, I guess or error feedback for the projects drop down, because you need at least one project assigned.

A

um So it would stay like that until you add a project, so you would add one and then you would be able to save changes and then, at the very end um it would switch it back into a a specific runner here and then you can see the assigned projects.

A

So that was a lot to go through I'm going to write the same thing and make sure it's pretty clear on the issue for the feedback that I'm looking for and uh if you have any comments, I'd love to hear them. Thank you.