 Okay, I think I'm ready. Let's see. Jacob are you all right? What's that? Are you okay? Oh, yeah, I'm in the hospital trying not to give anybody else a disease. It's not me. Cool. So the people who are immunocompromised. That makes sense. All right, so it's one minute past the hour so I'll just get started. Thanks everyone for joining. Happy Monday. I'll start with this slide. We have a new team member joining on May 3rd. Her name's Sarah. She'll be our UX lead so we're super excited to have her on board. Next I'm going to talk a little bit about some of the UX issues that we've been working on for 9.2. One of the larger features is related issues. The design uses the token that we have for our new search design and it will display the status of the issue, the issue number as well as the title. You can quickly add new related issues in a similar way that you can add a new issue to an issue board and in the future there'll be multiple types of related issue relationships including blocked by related to a part of and multiple others but this is the first iteration and it just includes one-to-one relationship that related issues us. We've also made some improvements to our markdown styling so you can see the current one on the left and the new design on the right. The new design is much more spacious so it'll really help with readability and we use the markdown throughout multiple areas of the site including comments, wikis, readme's, etc. So it'll really help improve readability throughout all these different sections. We're also working on lots of design updates to the customer purchase flow. The changes are mostly visual but it'll really help give the flow a more professional look. From this initial screen you can see that we've removed the red which really looks more like a warning. It seems pretty bad when you want someone to purchase something you don't really want them to stop or second-guess themselves so we've replaced it with cooler blues and purples and we've also added the pricing and cleaned up the pricing cards themselves and there'll be lots of other changes to the whole flow. With 9.2 you'll be able to run pipelines on the schedule and this means that you can set them for a time in the future for a specific branch or tag and you'll you can find this on a new schedule tab located under pipelines. This is related to the last slide but it's not currently scheduled for 9.2. I wanted to share it anyway since it's pretty related and the designs have already been worked out so one of the next steps for being able to run a pipeline on a schedule is being able to run a scheduled pipeline just once so you'll be able to choose between running a pipeline one time or repeatedly. We've started the first iteration of linking between project pipelines. I think I shared a little bit about this the next iteration in the last UX update but in this view it'll show which pipelines cause other pipelines to run by displaying inbound and outbound connections. With 9.2 we're allowing the deletion of protected branches. Mike talked about this a little bit in the kickoff meeting. We've added this ability because there's currently no way to delete a branch that is protected under a wild card so this forces the user to remove the wild card in order to remove the branch but this would also open up a possibility of problems with other branches that use that wild card so we've created a flow that allows masters to delete the protected branches. In order to do this you have to confirm in the confirmation modal that you see by typing the branch name and we're still continuing improvements to our search design. In 9.2 you'll see the avatar of the user when searching for an author and a sign. You also see the related color when selecting labels and you'll be able to clear a token by clicking on the X to dismiss it. So next I've included some projects that the UX team has been working on that currently aren't scheduled. One of those issues is improving mass editing of issues. I talked about this in the last UX update but I want to make sure it keeps getting traction because there's some confusion with mass editing since the filters look like how our old filters used to look so we've drilled down a design and you can check that out in the issue more. Another search improvement we've been working on is a new filter type that would allow for boolean type filters so this could include start issues, confidential issues, issues with a closing merge request, etc. This type of filter would give a lot of flexibility for adding different search parameters so in this issue we're talking a little bit about the wording so you can feel free to contribute. You can see from this screenshot we've talked about flag has is so we're just trying to drill that down. We've also been working on the ability to batch merge request comments. This would allow you to bundle and save comments until you're done reviewing and then you can post them all at once. So from the view here you can see a list of comments that you've already made and then you can click on a comment and it would link back which would allow you to quickly make edits before publishing them. One of the larger projects the team has been working on is improvements to our navigation. You've heard us talk a lot about it I'm sure already. In our testing we found that there's a lot of confusion regarding global versus contextual content so global refers to the navigation elements that are kind of always available to you so your projects, your issues, your merge requests, exploring GitLab and contextual content refers to the navigation that changes based off the page reviewing. So for example a group page has a different set of feature links than a project page has but because our global and contextual links often use the same language like you have your issues and you have project issues it's really easy for new users to get lost. So this isn't a super easy problem to solve. We've had two rounds of navigation testing to kind of determine where the problem areas are and then we've been having a few brainstorm sessions in order to create the mock-ups that you see here. Chris transformed these designs into prototypes that we are using to specifically test the global versus contextual problem. The major difference between these two designs is how we're displaying the project breadcrumb in the upper left corner. You can find both of the prototypes in the research issue which is number seven and so feel free to play around with those and we have a navigation channel if you want to share your ideas or thoughts there. So there's also a number of issues that the UX team has been working on that are ready to be implemented. I shared some in the last functional group update so I decided to just pick some more for this time. Part of that part of the work we've been doing is ensuring that our guide is constantly updated. Whenever we have a new guideline we want to make sure we add it so it can easily reference by everyone. There are a few guidelines that we've added that haven't been implemented yet so this is one of them. The idea is that within a dialogue or form the dismissive action is placed to the left and returns the user to the previous state so an example of that would be cancel and affirmative actions are placed to the right and continues towards the user goal and an example of that would be like save or continue or okay. Another guideline that isn't fully implemented is ensuring that each of our icons uses a tool tip so we just want to make sure that these guidelines are also seen throughout the website. When changing issue templates the issue description is currently lost and it's replaced by the new template. This can be really frustrated and lead to the loss of content if you're unaware that that happens. So in order to prevent that we'd like to add a confirmation step when changing templates. This would only happen if you've added content to the to the template that you're currently using and that would mean that changing templates would mean a loss of data so if you if you wouldn't be bothered by the confirmation if you change templates that haven't been edited. Responsive tables is something that I would love to see worked on. We have a design drilled down for the environment spews specifically which you can see here. Currently the tables scroll horizontally and they're very difficult to use on mobile or even on desktop some of the time so the new design would just show the essential information and clicking on the environment would display all of it in a new mobile friendly design. We also want to add time tracking to the milestone view. Last time I checked the issue has about 17 likes and it seems like a really easy win because the design is really simple and it just duplicates what you see on the issue page. So those are just some of the issues we've been working on or that we've worked on already so I'll stop sharing somehow and look through the chat. On the pricing page should we make a clear difference between you host and we host? Yeah we I tried to differentiate them but I will take a look at that again if it's not clear enough. Yeah I put that in I think like people might not know like what's the difference between EE and getlaw.com because we run EE on getlaw.com and stuff like that. I don't have a suggestion how to do it but I'm just afraid that might be yeah something people wonder about. Yeah that's a good point thank you. I answered Rebekah's question. Yomi I like your comment. All right let's see are there any any work for readability for long length? So yeah I mean that's directly related to the markdown stuff that we've been working on. I think that improving the readability there will help with the line length because there's just going to be way more spacing and it will everything won't feel so smashed together but we also do have the meta issue for the line link to continue the work that we've done there throughout multiple areas of the site. So we've done issues and merge requests and there's wikis, remes and a few others that where we use all the markdown. Any other questions going once twice getting a left. So we're getting a left nav bar again it's a possibility we're testing it right now. Great well I will give you guys all 15 minutes back of your day and I'll see you on the team call. Thanks everyone.