 So this is the UX functional update. It's a little bit late. It happened to fall on Memorial Day, so we moved it So it's a little bit out of order and you'll be seeing me probably Very very soon because this one got moved so much further ahead But that's okay. I can all hang out again pretty soon So next slide, please. I Have missed someone on the slide and I apologize profusely. I Have missed Hazel who is one of our UX designers I wanted to put out a list of all the UX team members There's a lot of new people coming in and there's so many people to meet and know Just so you can kind of get familiar with the names of different UX team members So Hazel Yang should be on here. She's fabulous Based in Taipei and I'll make sure that she's on there for next time Next slide All right, so coming up improvements for nine four next slide we're making a lot of merge request improvements in Nine dot four there's been a lot of talk about some inconsistencies and some different areas that Does somebody have their microphone on that's me hold on I'm trying to figure out No worries no worries, I think that's a little bit better Is Maybe Sid can mute me. I think Sid can mute me. Maybe I can I mute you? Are you the host? I believe I am okay, then you can mute me. I can mute you This is a fun one guys. I gotta say this is a pretty good I'm gonna mute you let's see. No, I can't hold on So I'm gonna keep talking about merge request widget improvements So we have a meta issue for this. There's a lot of different issues that are tied to it We're trying to take a holistic view so that we can make sure we're making improvements that make sense for the entire Area rather than focusing in on just one or two little things. So here we've got some improvements to making merge warnings easier to understand easier to take action on Making sure that the spacing between items is consistent so that when you're viewing it It's it's a lot smoother a lot more polished looking Next slide Member roles per project so in our user testing it revealed that users had trouble knowing their projects membership Who's the owner master developer and they weren't able to quickly tell which projects? They were a member of when exploring projects. So this just seeks to make that a little bit clearer by adding The little label next to it in both the membership labels and project lists You can see whether a developer owner master etc next slide So new design approvals Settings in the merge request form Updated design so that you can set the number of approvers as well as adding and removing approvers And that suggested approvers link is now going to be right below the approvers search box. So it's a little bit easier to find Next slide So there's been a lot of talk about this one trial and license purchases inside of git lab EE This is part of making EE the default download my disclaimer is that anything you see here is still a work in progress So this flow may change may be updated So don't take it as the single source of truth quite yet Once installed users should be encountering EE features if they don't have The license for the EE feature they get a summary of that feature and a call to action direct them to start a trial of EE It's not permanent. We don't intend to nag users with something like this if they indicate They don't want to do a trial. They're not interested in EE these areas will simply be grayed out and they won't have To be bothered with it again But the the purpose here is to make them aware of the features that we have that really can improve their workflow Next slide So when they do opt for the trial they can do so without a credit card So there's a simple form that allows them to log in Or sign up very quickly and then start get started with a trial without the hassle of having to put in a credit card and Worry about whether or not they're going to be charged for something, right? Next slide Inside of the admin area under licenses once the trial has been activated They'll be able to check the status of the trial by a license upload a new license in the admin area Again, this is all kind of a work in progress. So this may change But in general, this is the road. We're going down that design lies next slide Milestones so we currently have no native notion of group milestones instead when we create a group milestone We're really creating multiple project milestones and this Design aids to aims to make this a lot easier of a process one would be a milestones dash That's up at the top the screen simply adds a message explaining which milestones are being shown Group milestones page combines group milestones and milestones from all projects in the group We show all milestones in the same list the simplest approach for first iteration When assigning a milestone on an issue, we'll show the group next Group name next to group milestones. This way we can differentiate group and project milestones Which belongs to the same scope as the issue Next slide So in this one we actually this is a merge request waiting to be merged in it is good to go Here we've removed the duplication for sharing projects with groups inside project settings You can see the before and after there was just simply a duplication in there That wasn't necessary and made the page a lot longer than it needed to be Next slide and then we have a ton of UI polish issues that we're working on here are just three of them The fourth is listed, but there wasn't really a way to to visualize that one So one of the things we're working on is improving the line length inside of GitLab So making sure that areas of text are easy to read. They're not excessively long And that they don't make the page longer than they need to be Another is making the hover focus in active states consistent and the icon for the drop-downs should also be consistent And then making search consistent a consistent experience across all of GitLab as you can see in this little gif We have here. There's actually three different types of searches right now So we're looking for a way to combine those together and make it an expected experience So next slide. So I do something a little bit different here I'm going to let Dimitri take over and go through this next section of unscheduled UX issues already currently in progress And then I will wrap it up at the end with those items that are UX ready Take it away Dimitri. All right. Thank you, Sarah Yeah, hi. Welcome to the UX functional that I'm gonna cover The part of unscheduled UX issues. They are a work in progress I'd say not all will go in there or in full capacity Can we go to the next slide, please So here we are at the navigation and the navigation is a pretty pretty big concept that's being worked on I have to note here that these screenshots are grayscale. They're just as intended for design purposes for exploration They will will not be final as for what is going in The purpose what we're going to do with the navigation is getting a clear distinction between contextual and global Navigation and within this mock-up or screenshot you can easily see in the black navigation the global navigation This will be visible in each view. It will be easily easily be able to go to different dashboards such as the project's dashboard groups or activity and the final end of this is to be able to be To make it easier for users to know where they are in the application And to extend on on that I would like to go to the next slide to see the contextual navigation and the contextual navigation is once again and move back to the sidebar and it's Again, another clear distinction between global and contextual navigation It will have both functionality of When hovering over an element to see which sub-elements will be visible under that On that elements, I'd say so if you go to issues Currently, it is quite a big problem to go to for example the issue board You have first have to go to issues It will open up the list and only then you can select board. This will try to improve that and in the in the process improve the Go ahead and so tick application. So knowing where you are next slide please and the top at the top mock-up you can see the The breadcrumbs in the application. You have global breadcrumbs. You have contextual breadcrumbs. They will be displayed under each other They will move towards the content area, which means they will be scrollable with the content So they will not always be in view But they will be there when you open up new view to make you aware where exactly you are again Let's see next slide please So this is the merge quest View this is gonna be this is purely an exploration by the way This intends to make it less crowded to make it easier to digest which view you are looking at to easier to make it easier to Skip to the content you want to read for example You may open a merge quest view and only want to skip immediately to the changes to see the diff of the actual Merge quest you're trying to get merged or you're trying to review Some other changes in here are The merge quest widget which is a famous UI element in this view which has been changed to a tab This is purely an exploration for now. This needs some more discussion But there we're looking for ways to improve how efficient a person can be on this page Next slide, please So this is when a user sets up a new instance And they are agreed with okay, you are going to be the root user of the GitLab Instance you are created we want to have that be improved and Let's see and if you're a registered user there will be a different view But this is to improve the onboarding experience. So to say Make now that if I have any mistakes Sarah will improve it will correct me of course next slide please Lastly for the improvements or work in progress section of this functional group update is the project importing from GitLab and come to your own GitLab instance, so to say you start out on gitlab.com eventually you say like okay, my Business is growing grown quite rapidly. I'm going to need my own GitLab instance This is for you, and you will be able to more easily import projects from GitLab.com towards your own instance Clicking on the link will open up a new tab and won't change your contextual view So to say which is quite important to not break the user flow And onto the next slide. I'm going to give it over to Sarah again Awesome. Thanks to me tree really appreciate that in the future. I'm actually hoping to have UX designers rotate and each do one section just to Get a little bit of a different voice and a little bit different perspective on things as we move through So UX improvements ready for implementation next slide, please So these are all issues that are sitting out there UX is ready It's just waiting on some nice kind person to work on it and put it in to GitLab so the first one is highlight all matching substrings in auto complete drop-down. So that is a mouthful So right now when you mention a user the drop-down pops up to help you, but it only Highlights the user handles it doesn't Also highlight their full names So we want it to match All the highlight all the matches within those substrings right so that it's easier to quickly find the one that you're looking for Next slide So displaying time tracking totals on the milestones page I'm going to show the aggregated values for the time spent time estimated time remaining That way you can assess the milestones progress based on the open closed issues and Timetracking is possible by looking at the issue counts progress bar and time tracking stats Next slide Confirmation dialogues. So this are actually two related issues to improve our confirmation dialogues The overall appearance the messages that they display as well as the actions you can take Making it very clear that when you're deleting something or removing something that that is an action That you won't be able to undo Next slide and then resolvability of discussions and issues so when creating a discussion You can actually indicate right now that it's resolvable when you resolve the discussion you truly resolve the entire thing There's not a concept within this of individual comment resolvability It applies to issues merge requests non diff commit snippets If a single root comment has no applies, it'll still show the reply panel So we use it can easily reply jump in etc So now I'm going to open it up to questions next slide. Let me take a look at the chat No questions anybody anybody Curious about anything. All right, there's one more slide and feel free to jump in with a question of you think of one. I Want to give some shout outs. I saw that Lee did this and I was jealous So I went ahead and put together my own shout out slide And for next time I'm going to have to put a shout out to Jacob for saving my butt in this functional Group update because otherwise I wouldn't have had all my speaker notes But we've got a lot of people out there working to help us implement these new designs So just some people that we've recognized lately have been doing a lot of great work helping us Annabelle improving table issues I'm grilling. I'm going to say Mike because I don't know everyone's name right now started working on improving our settings and Phillipa went through all the UI polish to make sure that we had everything in there that we needed to get those out in the next release Which is a huge effort And the product team, I don't know how much shout out they usually get but I want to say a huge Thank you. They've been fabulous about getting together with us to talk about how we can work better as a team to get Get things moving faster for UX so we can get a little bit ahead And Phillipa says it was a team effort shout out for Tim and Clement. Yes, absolutely I will make sure that we we highlight them next time So if there's no questions, I'm going to say that this is it. I promise next time. I'll be Ready with an extra screen. So I'll have my speaker notes And I just want to say thanks to everybody for attending. Have a great Friday. Bye. Bye