 All right, I'm going to go ahead and get started. It is 11 o'clock for me. Anyway This is the UX functional update. I Added the link to the presentation in the chat. I wasn't able to update the calendar invite So my apologies on that one, but if you're curious, you can go ahead and link to the presentation there Start out with my team slide. So anyone that's new. This is the UX team No particular order and I just wanted to mention that there was some strange Scheduling last time due to Memorial Day my functional update got pushed So we actually went over the majority of 9-4 in our last update So I only cover maybe one or two items. So if you want to go back and look at the 9-4 Items that we covered last time there's a link there for you So I think this is the only item that I've added from 9-4, but it's it's a pretty neat one So coming up, we've cleaned up the issuable lists The goal here was to adjust the layout so the labels wrap nicely as the screen sizes reduced So less clutter a lot more polish easier to see on smaller screens So there was a lot of feedback On the confidential banner redesign, which was released in nine dot three You might remember that that lovely black bar that would follow you as you went up and down the page The redesign sounded good in theory, but it was really intrusive for users when we put it into practice So we rolled that back the goal here really is to let users know that they are viewing a confidential issue Not to distract them from the task at hand. So in this new design the icon is In the header as an with an orange background. You can see it right here Makes it readily visible, but not obtrusive once you scroll It moves from here down to this bottom right-hand corner So it fades and it moves to that bottom right the banner only appears when scrolling in the background of the banner is Transparent so it's not covering up anything and it's not really loud and in your face And really we're thinking that confidentiality matters most when you're leaving a comment, right? You kind of want to see who's going to be able to see this comment So the confidential issue banner will fade out when the comment box is opened and the comment box will now have a Confidentiality message to alert users that they're making a comment on a confidential issue then in the sidebar is how we're going to Control whether it is confidential or not. So if you look here in the first when the issue is confidential There'll be a little eye icon. It'll tell you it's confidential and you have the ability to edit that So when editing that you get a confirmation You can go ahead and cancel Or turn off confidentiality which will then make it visible and we changed the verbiage a little bit tried to keep it really simple So if it's confidential, it'll say this is confidential If it's not confidential, it will just say none. Nothing has It's not confidential Felt this was a little bit easier to see and understand pretty quickly Navigating files in merge request diffs. This is one that I think will make a big difference So in the first screen here, you'll show you'll see that it's showing how many change files were changed How many additions how many deletions? We want to keep this accessible at all times. So when you scroll It will dock itself right here with a little drop down and over on the right-hand side You'll actually see the x additions y deletions will be shown in a quick and easy to understand format Sorry about that after clicking The little drop down you'll get the ability to search and look through all the different files So you can look for specific additions nations changes that were made We also improve share locking feature for subgroups So when a parent group has a lock on sharing projects with other groups, this restriction should apply on the subgroups as well Subgroups should be able to apply a lock if the parent group does not have one Subgroups cannot release a lock if the parent group has one and the UI will explain this to the user So it's very clear what they're doing. All right. Let me just check and chat real quick All right, so I'm scheduled UX issues currently in progress Transactional batch merge request comments So we're trying to prevent notification overload by grouping comments staging comments and then submitting them all At the end that way you'll only get one notification instead of a gazillion of them Multiple discussions per line in merge request diffs. So currently in merge request if she can start a vertical line of comments It's essentially one discussion So we're going to enable the ability to branch out to multiple multiple discussed discussions. Sorry about that So early for me For each of those discussions enable resolvability and remove the ability to resolve individual comments So going forward you can only resolve entire discussions And this is just one example of all the ways that we're going to make empty pages awesome everywhere in GitLab And then we have some mobile optimizations for the merge request widget It's the first iteration towards improving the merge request widget for smaller viewpoints viewports, especially mobile We're doing a lot of work in the mobile area trying to optimize and make sure that things are clean and clear and easy to use So UX improvements ready for implementation Right now we have a hundred and twenty four open issues with the UX ready label so this one another beautification of empty screens It's actually logging in user when setting up a new instance. We've redesigned this to include text On the downloads page and command line telling the user where to go after installation Tory did some great work going through this to really understand what was confusing and what was difficult for those first Coming into a new instance So we've improved the first page as well by including the username of the admin was in the details to begin with But it was easy to forget by the time you get to the stage And allows them to create a password and automatically log the user in This was here last time. I'm just going over it again. It still hasn't made its way in has 30 likes It's currently in the backlog So display time tracking totals on the milestone page Show aggregated values for time spent time estimated in time remaining Assessing the milestone progress based on open-close issues and time tracking is possible by looking at the issue counts Progress bar and time tracking stats. This has a lot of really really positive comments on it So it'd be great to get it in sometimes soon These as well haven't quite made its way in yet improving our confirmation dialogues keep users from making mistakes with clearer Directions and instructions on what's what's actually happening when they click a button and Any questions on any of that what I'm actually going to do next is go over the UX okay ours that we put together Kind of explain how we came to those okay ours And then what issues will be working through to support those Any questions I'm gonna keep moving all right So okay ours So the first step we took was to look at the high-level objectives to determine where UX could offer support Objective one relates to sales and numbers and while good UX certainly contributes to increase sales and revenue We need to be able to track specific initiatives and objective three Relates generally to recruitment and hiring company-wide, and I think we have an awesome team But I really felt like UX needed to focus on objective two for this quarter so underneath that objective there are CEO objectives, so the first CEO objective relates mostly to performance performance of get lab comm and and our Our product in general so we focused on the other two objectives From these I identified or we identified Usability goals that will allow us to develop get lacks and get labs UX vision and strategy so this is how we kind of worked through each one so I Took or we took the the overall objective and we kind of broke it down to what problem is this talking about So what are the problems? That are arising that's not enabling this to happen Then we lay out how get lab is a business can solve these problems So this allows us to then define specifically how UX can support these business goals And then as part of the process we also make sure to define how we'll measure whether or not we're successful in attaining these goals and Sometimes that can be a little bit more tricky in the UX area Then and maybe other areas right we need to have very specific stats. We have to have starting points and understand where something was Before we made a change and then reevaluate after it after the change So from this whole process of kind of looking through to defining the problems the objectives how we can Assist we come up with our final UX. Okay are and this may be different for each team. I'm not sure how the other teams Went through and did their okay are so be interesting really to see how other teams kind of focused in on these So the first UX okay are is to make it easier to find and use advanced get lab features And I've just put some of the issues related to this Some of have been completed or in process and are in the future Improved navigation iterate on it every month and these are again are just some of the issues I didn't talk about navigation today because we're still in the midst of kind of really putting together colors and Implementation getting the feature toggle in there. I'll talk about that extensively in the next functional update Improving perceived performance I think that there are definitely areas that we can assist in helping where maybe performance Seems to be lagging and we can assist with some UI elements to make time Seem to go a little bit quicker. There's always going to be times when something takes a little bit to load skeleton loading Loading of issue title and description before the rest of it gets in there can really help with that Then this last one is is rather large so measure usability of critical user flows to identify areas needing improvement There's kind of two little sub subsets to that. The idea here is to get really good concrete research done on critical areas and Identify where our users are getting stuck where things may be confusing or we may be able to save them time and Enable them to get what they need to do done a lot faster So we have a UX research roadmap that we have put together and the way this is going to work Is that each roadmap generates three or more areas of testing so in each roadmap? We're not just testing one area right now. We're testing Dashboard notifications and merge request and that's all done in one release cycle So each release cycle will be testing anywhere from three to maybe up to six different areas gathering information and then finding ways to Optimize and adjust those flows questions comments thoughts I Need Larry in here with a laugh track. That'd be the best. Where's Larry when you need him? All right fantastic last slide shout outs It's we had a condensed amount of time between our last Update so I don't have as many shout outs, but I wanted to thank Marsha and And Jay Vargas for helping with the new blog theme and helping Dimitri write his fantastic Travel around the world blog that he just released last week So really appreciate that All right, I'll let everybody go Hope everyone has a great week. Thanks. Bye. Bye