GitLab UX Team, 30 Apr 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Plan UX update - 13.0 - Portfolio Management

Description

13.0 Release Planning:
https://gitlab.com/gitlab-org/plan/-/issues/85

Add hierarchy depth to roadmaps:
https://gitlab.com/gitlab-org/gitlab/-/issues/213401

Epic swimlanes:
https://gitlab.com/gitlab-org/gitlab/-/issues/7371

Metadata organization:
https://gitlab.com/gitlab-org/gitlab/-/issues/215042
https://gitlab.com/gitlab-org/gitlab/-/issues

Reduce Epic Health Status "Noise" in Epic tree when no statuses are assigned:
https://gitlab.com/gitlab-org/gitlab/-/issues/214675

Show epic information in issue list:
https://gitlab.com/gitlab-org/gitlab/-/issues/10482

Filter Roadmap view by set dates instead of infinite horizontal scrolling:
https://gitlab.com/gitlab-org/gitlab/-/issues/204994

A

Hey there I'm Alexis Ginsburg I'm, a senior product designer at gay lab working within the plants, age and more specifically, working in the portfolio management group within plan. If you look at our compound board, you can really see what we're working on more specifically. If you look at the workflow design column, you can see what I'm focusing on any given time. This is separate with the highest priority items being at the top. You can also look at our release issue, so this is everything we're hoping to release in 13 point now.

A

You can see for each group, so you have portfolio management here. You also have project management which Hollies working on and certify which Nick is working on. So this is a great resource, I'll jump into this within thirteen point, oh one of the first items in the list is book editing, issues to assign or unassign and epic. So this will look familiar if you work in issues a lot.

A

Basically, we just want to allow users to book assign epics to issues so I can select many issues in the list and say I want to put them within an epic we're also working on well we're doing a lot of work in epics to improve them. First off. We want to allow users to easily create epics, so this is all around having a new create epic page so similar to issues again. I can say just let me create a new epic, and then you see this epic creation page, and this is pretty simple right now.

A

This is MVC, so we're gonna keep building this out, adding the epic option when creating a new issue. So the flip side of that is that when I create a new issue, I might want to say what epic it's in so I'm, creating something I can select within the drop-down which epic that issue belongs in including issue in sub epochs when filtering by epic. So if that in the issue list, I'm filtering by a specific epoch, I might also want to see which children are within that epoch. So all epochs have child epochs.

A

Not all, but if you assign child epochs within an epoch, you can see them here and there's going to be a denotation. If that's a child, epic nap or a parent, epic I should say so. New epochs can be created as confidential. Again, this is very MVC, so we're going to keep building this out. I might drop to this one as well. So there's many issues within this.

A

This is when I'm working on within probably 13.1 or beyond, but really the idea of this holistic approach to confidential epics and matching the interactions we have within issues and being really intentional about what does it mean if I toggle on an existing effort to confidential? What does that mean for the issues within it or what does that mean if I take an issue out of a confidential epoch? So things like that, we haven't quite figured everything out, but we're taking a very MVC approach to that with.

A

This issue right here also this one- is really cool and I'm reviewing it at the moment, one of the front-end developers right now it's working on this, so allowing changing, read, bet, elbowing, changing item parent, epic, so I have a parent. Epic I have children underneath it. What if I'm in the epic tree and I want to reassign that child epic to another epic? You can't do that currently within the epic tree, so this is allowing for that.

A

So within a drag-and-drop interaction, I can change the parent epic of an issue or, if sub epic, and if you get tired of me, saying epics I'm, sorry because we are gonna, be working on this for a while, so consolidating epic tree buttons. This one is pretty exciting too. So, as we add more information to the epic tree, we really wanted to simplify that interface, make it easier for users and make it more friendly for smaller screens.

A

This is one of those attempts so instead of having the two buttons we're just going to consolidate, it's one add button. The experience after clicking one of these options is pretty much the same. For now for MVC, so adding hierarchy dub to roadmaps this one is really exciting to me as well.

A

So now at the moment, you really only have the option to see the parent epic within the roadmap, so we're gonna keep working on this so that you can expand the parent epic and see all the children epics underneath it and then eventually you'll see the issues etc. Underneath that maybe even tasks at some point.

A

So that will look something like this and I think this is within the mr stage as well, which is really awesome, I'm, reviewing it reducing the epic health status noise in an epic tree, so we just released the epic health feature. That's really exciting. It is MVC, though, so we're going to keep iterating here. Some of the feedback we got is that really it's kind of noisy? If there's no health status defined or a science here, maybe users don't want to see that within epic tree? So how might we simplify this?

A

Do you know, isn't declutter? It I think the solution right now is basically, if an epic doesn't have health status defined we're just not going to show that health status. So you can see that there's an epic here, we're not showing that health status within it and we're actually going further to simplify that by just showing the badges instead of that entire label of issues or showing the title of needs attention on track. Stuff I got so just simplifying that interface a little bit.

A

The assumption here is that this legend I'm calling the legend at the top in the header, is enough to indicate what those badges mean.

A

So the issue cards and the epic tree have two lines of content. This is further expanding on that epic health feedback. We got we're adding a lot of metadata to the cards and the epic tree and within gitlab in general, in those widgets. So thinking about how to better structure this content, make it more readable, easier to scan. So first attempt here is because we know those titles are really important to users. You know that's how they differentiate the cards from each other.

A

That's really what they're scanning for on first glance, really make room for that. Don't let it truncate too early. The idea here is actually that I will wrap and the title might go multiple lines, but it's important for users to see that title and then thinking about what the metadata to look like within the card. So that's still in progress.

A

Current ideation is, you know having it wrap and really the next up here is doing a lot, and you know, hopefully you concur it, but doing research into what information is really important to see here for users and what information they need to see within each widget. You can we get rid of some of this metadata.

A

You know. Do we need to show this at all times and then thinking about the priority of all this metadata like what our users in see? First, what do they expect like? How do they rank this information? So that's in progress right now on the outside, also in progress. This is a larger chunk of work. Is epic swim lanes within a board, so I showed you the board earlier.

A

This would be within this view, and it would just be adding another dimension which is swim lanes, so basically having rows like cutting this information into rows by epic. So this one is interesting, I'm currently working on this right now and if you have any feedback, please leave it open another issue here, that's just all around the design of these swim lanes, and this could look something like this.

A

They make this a little bigger for y'all, so.

A

You can see there's the epic here and then all the issues that fall within the epic show up underneath that, but swim lanes and they're still going throughout the workflow. So that's interesting part of this, so it's just adding dimension to the Kanban board. It's not entirely like a new feature or a new way of looking at it. It's just like looking at the data and it's a tiny bit of different way.

A

So filtering the roadmap view by set dates instead of infinite horizontal scrolling. If you've been using the road map, you might notice a few performance issues. This is part of the way to alleviate some of those, and this is in progress from a UX perspective, but these states allowing users to say dates on a calendar or whatever I'm, not sure, definitely would look like yeah, but user set dates that they care about and really zooming into those dates. So I might care about this month.

A

Right so I want to see I guess it's April 30th now, but I want to see April 1st through the 30th. This is not that care about that's my view.

A

Instead of seeing basically from the beginning of time until the end of the time as it is right now on the roadmap toggling, we talked about this before so really looking into the MVC of confidential epochs expanding that out further, you know pushing this past and BC, and this is a cool one, since we are really focusing he'll be in the next three notes, or so within the quarter on epics, if you ever have feedback on this maturity like these are the assumptions we have that we'll get epic category maturity up like these are the things we think users care about and we'll make epics more mature.

A

So if you have any feedback on this, leave them in the issues of epics attached here and of course, this tree is gonna get even better, so that is basically what I'm focusing on this milestone. There's a few things here there that I may have missed, but always feel free to reach out to me. If you have any questions or collaborate on anything, but that is portfolio management UX this month. So good talk with y'all see you later.