Hi everyone, my name is sarah waldner and I'm the senior product manager at kit lab for the monitor stage in the health group, and today, I'm going to run us through a speed run for the new manual incident creation workflow that we're getting ready to release in 13.3.

So I'm typically the incident commander for my response team and uh we keep the tanuki ink web app up and running for our clients, 24 7.. I just heard from the support team that a lot of customers are experiencing intermittent load times and they keep getting poor error codes on pages that our service provides.

So I didn't receive an alert for this. This is one of the times where it's really helpful to be able to create incidents manually so heading to the incidents page. I'm gonna go create an instant. It's gonna prompt me with the issue. Template called incident because I have that so for for any projects where there exists, an issue template called incident manual. Incident creation is going to pick that up and apply it if it doesn't. Have that then we'll just create.

However, other issues create another thing that we're shipping in this milestone is incidents which is a new issue type. This is the first issue type of its kind within gitlab, so you can see a lot of the same features that issues have, but now it's an incident gives us the ability to customize the experience so back to the speed run. um So, let's see nuki web app uh experiencing intermittent load times, I've got my correct issue: template pulled up um details supported by support team.

Support case I'm gonna get the information after I get this going and get my team on it. um I wanna keep track of this. I'm gonna go ahead and set it to myself.

Awesome uh so I've got my new incident up. I want to get our zoom room going so that people have a place to synchronously collaborate while we're resolving this, so I'm going to slash command. Add the zoom room.

So now my team has a way to hop in when they need to, and then I'm going to publish this to our status page so that people know that we are on it.

So I've got my incident published in status page as I update my incident. Changes are gonna populate here um and then back on the incident I'll get some team members.

Involved, I'm also going to check out to see I thought that I saw in our incidents list yeah we have something else. uh Another incident that's going on right now, so probably want to grab that and then mark it as related to the one that I'm currently working on.

So you might want to merge these in the future, but for now I'll keep them separate, because it might be two different instances, I'm not sure who created the other one. So I'm able to connect the related incident. I've got this up and going I've got team members coming. I've informed our customers and I've given us a place to synchronously work on it. So thanks for watching that is manual incident creation and the new incident list.