GitLab Protect Stage, 2 Sep 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: defend UX prototype: changing alert status and quick actions

Description

Related epic: https://gitlab.com/groups/gitlab-org/-/epics/3454

A

Quick follow up here, focusing on changing statuses, um and so so, first in the layout, the first way to change the status would be to actually uh just change the column. This way in the kanban the drag and drop another way is if the user goes into the details, we see some call to actions up here and some details about the alert here now. This drop down the user from here can change the status from this.

A

There is also this quick action for dismiss that is just in the unreviewed, we'll take a look at that in a minute and then the ability to create an issue around it in the previous version, um the interaction what we were trying to figure out is: how does it work when changes are made on this page when the user does these actions such as dismiss or status?

A

um Does it auto save and, and how do you have to have a save button? How does it work, and so that's what this interaction is focusing on. So let's say that the user determines, after looking at the details here, that they want to change the status or take a closer look at it.

A

Let's say, for example, they want to change it to under review. So let's do that right here. So we see a couple. Things happened.

A

We had some feedback in the background of that change, so this actual tile is put at the top of the under review section and it removed the quick dismiss button and it didn't close the drawer so and the reason there is is from here. The user may want to take a closer look at the details or they may want to go ahead and create an issue around it um or just have it open as they may investigate it further by opening it up opening another tab or what not.

A

So that's the reason why the drawer doesn't close okay. So let's close that out and let's take a look at the second one, so here's the case- let's say the user reviews this and they determine that it's a false positive and they want to dismiss it.

A

So again, the dismiss is only displaying in the unreviewed section, because that's the the place where dismiss action would be um performed, the most so surfacing it out from the status it's still in there, but since it's kind of like a quick action um to be able to just take care of that quickly and not get out of their workflow, and that would work like this, so the user dismisses it. It removes it from the column and there's a toast message here, just to confirm that that was done and an undo option.

A

Okay. So let's take a look at this one now, the one that we moved over to under review again, they can change the status from here view, an issue which will go there. There'll be a separate um there's, a separate issue for that workflow and I'll post the designs here. But um then let's look at the the confirmed column. So this is, if um you know, as the as the status says, is if the alert is confirmed.

A

We open this up and we see a quick action here, that's mark as resolved and that's similar to the dismiss, if it's in the confirmed column um that you know the quick action from here that would take place the the common one might be to mark it as resolved once it's done and that'll have a similar uh feel as the dismiss where once that's performed down.

A

Here we have the undo option and the messaging to confirm that it's done so yeah just uh any thoughts there on that workflow how the status has changed um if it's necessary to have those quick actions, if you think those are beneficial, those are kind of the questions there and yeah. Thank you.