GitLab GitLab 13.7 Release Kickoff, 17 Nov 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 13.7 Kickoff - Plan:Product Planning

Description

Link to issues mentioned: https://gitlab.com/gitlab-org/plan/-/issues/201#product-planning-christen-kickoff-video

A

Hi, my name is christine debenko and I'm a senior pm in the product planning group in the plan stage at get lab. This is our 13.7 kickoff in product planning.

A

We do have shared capacity with, but when we have our split between our two groups, we were able to prioritize some really good stuff for 13 7., I'm going to go through two of the bugs that we're prioritizing and then we'll get into the group theme for the product team product planning team.

A

So the first prioritized bug is when adding a sub epic from a subgroup. The wrong epic is added, I'm going to show what this actually means just with a diagram here. So if we have a parent group with a subgroup inside it and the parent group has two epochs one's called id1 apple id2 banana and then the subgroup has another id1 cherry and then we take this scenario and we did want to add an existing epic of cherry up here into the banana epic.

A

So we would do that by saying add existing epic and we'd search. Cherry we'd choose it and click add, but the bug is that it would actually link to the the apple epic, so it's using the number one id and it's pulling in and linking to the epic within the same parent group.

A

So you would end up with the apple linked like this, so it's a really important bug to fix, as it's not expected, behavior at all that that is happening.

A

The second bug that we're prioritizing is ensuring that we don't show a warning when there are less than a thousand epochs on a roadmap. So if we look here at this warning, this has been coming up even on filtered roadmaps, where there may only be 50 or 60 items.

A

So the team is going to look at this troubleshoot figure out what's going on and just make sure that this does not show up unless you truly have more than a thousand epics in the view at the time.

A

So those are the bugs. The second area is our group theme, and so in our group we are working on building out epic and program boards, which is really important to our customers, who want to be able to have boards just like issue boards for their epics.

A

So if we are to look at the entire epic here, it's called epic and program boards for 13.7 we're getting into allowing users to view epics within their board, and a lot of these are prioritized for 13 7 and 13 8.. um We're also focusing um while this theme is for our users to be able to achieve this. We actually have to re-architect onto graphql.

A

So a lot of the work for that will also be done in thirteen seven and then beyond that we'll get into creating and deleting boards um allowing users to create new epics within the board and beyond, but for 13 7. The focus is going to be around viewing and as well as the graphql migration.

A

The last section here I wanted to talk through is technical debt reduction. I wanted to point out a road map. Speed up, render time issue that we're looking at it's actually really complicated and very heavy to be scrolling left right, as well as up down on a road map.

A

There's a lot going on that can really slow down the rendering time. So the team is going to look at splitting out two virtual lists in tandem, one for vertical and the other for horizontal scrolling and try to speed this up. If we get the render time down and it's faster, then it opens up filtering by milestone.

A

um We can do a lot more advanced filters up here, right now, they're way too slow when we do those things. So it is technical debt, but it's actually going to unblock more user features, especially a milestone, filter and some other search capabilities within the roadmap view.

A

All right that is it for the product planning team for 13.7.

A

We hope you have a great release. Thank you. Bye.