GitLab Source Code Group, 21 Jul 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Remove, add, and explore - 13.3 Create UX team updates

Description

Pedro Moreira da Silva, the Sr. Product Designer for Create:Source Code, shares the issues that he will be working on for the 13.3 version of GitLab.

Create:Source Code is the area of the product that deals with merge requests. More specifically, merge requests fall into the Code Review product category. More info: https://about.gitlab.com/direction/dev/#create-1

References:
1. Remove “Jump to next unresolved thread” button in merge request threads: https://gitlab.com/gitlab-org/gitlab/-/issues/199718
2. Evaluate removing/hiding file header buttons in merge requests: https://gitlab.com/gitlab-org/gitlab/-/issues/199725
3. Display change that made discussion outdated in-line: https://gitlab.com/gitlab-org/gitlab/-/issues/24468
4. Document issuables existing semantic grid: https://gitlab.com/gitlab-org/gitlab-design/-/issues/1223
5. Document issuables existing conceptual model: https://gitlab.com/gitlab-org/gitlab-design/-/issues/1222

A

Hi, my name is pedro morera de silva and I'm the product designer for the source code group in the create stage of the gitlab product, and today I'm going to share with you the issues that I'm excited to work on and the current milestone 13.3, which is the next version of our product.

A

And today I'm going to talk to you about three things in particular. One thing that we're removing from the experience one thing that we're adding and another aspect that we're exploring in the user.

A

Experience of merge requests, but also issues epics and all objects that are very similar in nature, with a content area and a sidebar, and we call those issuables it's the type of object, and so first, the one we're removing so we've put in some some telemetry to um gather data on how much this button is being used today, and this is inside the merge request discussions.

A

uh You have this button to jump to the next unresolved thread and you can keep clicking these buttons that are available at the bottom of each thread to jump to the next into the next and so on. But you also have a global button that is available at the top, as you can see here, and the data tells us that if every time this button, the one at the top- that is global and is sticky every time that it is used.

A

This button, which is available in each thread, is only used about seven percent of the times. So it's usage is very very low. So what we're going to do is remove this button behind the feature flag. The one available in the threads see what is the response and and then consider completely removing it uh from the ui.

A

So that is one thing that we're doing and we track the data for about four months, we're also evaluating removing other buttons or hiding them from the ui, and so there's this issue as well, which I'll paste in the references. If you want to see um one thing that we're adding that I'm really excited about, it doesn't have a tremendous amount of design work.

A

It's mostly showing, and you reusing components that we already have and people are used to in the gitlab experience and it's in the context of a thread that is commenting on a specific line of a file that was changed when that line is then eventually changed in a new commit in a new version.

A

We currently don't display the change that was made, and so this issue is to finally show a little uh preview of the change that was made after this discussion was started so that you can see the changes evolving uh based on the discussion that people are having. So I'm really excited about this new thing that we're adding this enhancement, um and I think it will save people a lot of time and it would be very productive.

A

Some, a couple of things that we're exploring are documenting the issuable's existing semantic grid.

A

So, as I said, um issuables is kind of the category of objects where we place uh issues, merge, requests and epics and those are kind of the main places for discussion and where work happens inside of kit lab, and so we want to document their semantic grid and the semantic grid is basically the visual placement and layout of the primary objects, the local and global action and the attributes of those objects, and you can see in this work in progress, figma file that I'll show you here.

A

The work that I've been doing in documenting and highlighting the different areas pertaining to navigation and location attributes, object, relationships, activity, uh global actions, local actions, and this is a work that I feel we need to do. First before we evolve, and so I think it's really good to see this and then compare with the redesigns that will happen over these different uh issuables, so merge requests, issues and epics and you're free to explore this figma file.

A

It should be open to to everyone, and then parallel and very similar to this issue about the semantic grid is just documenting the conceptual model and that is just defining the objects themselves and the actions available and also enumerating the attributes for every object. So this is the visual representation of the conceptual model. The conceptual model will likely expand on that and be more detailed. This is more the visual placement and the layout of these these terms, and these things the objects, actions and attributes so yeah.

A

This is what I'm excited about, um feel free to comment on in this issues, um also in the kickoff update issue itself and yeah. If you have any questions, if there's anything, I can do to help. Let me know thanks for watching and see you next time.