GitLab Plan Stage, 17 Mar 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 12.10 Kickoff - Plan:Project Management

Description

Plan - 12.10 Release Planning Issue - https://gitlab.com/gitlab-com/Product/-/issues/894

A

A

Weaver here, project-management p.m. doing our 12.10 kickoff call.

A

This release is going to look fairly similar to what we're prioritizing for last release, with the caveat of focusing on the jury importer, so real, quick running through I'm, probably problem validation, we're gonna, try to sort out how to best handle label, duplication of label promotion, a lot of weird things that are happening with that as a result of when projects move when groups move and along with that we're going to look into properly in the looping issues in terms of solution, validation, the biggest complaint that we've gotten from customers that I've spoken to recently is that the milestone view is not historically accurate.

A

So the first step we're taking that we will be releasing until that's in is a burnt-up chart two milestones and then, after that, we need to revisit the mouse of view entirely. It kind of free design, the UX around surfacing data that is more valuable to folks that are doing time, boxes sprints and need to understand how things evolve during the course of their sprint or time box.

A

Design parties we're going to also focusing on tracking scope change within the milestone in terms of features that we're focusing on delivering 12.10 talk to initially about adding charts and milestones, and this is more or less so. You can see on the graphical view what scope has been added to a given milestone and how the scope is changed is a plot data plot, along with what has been completed, and so ideally you'll go see if scope was added if it was removed and then how completion is tracking against the scope. That is it.

A

The current milestone. The other kind of long-running thing that we're working on is viewing real time updates of assignee and an issue merge, request sidebar, so the assignee is up here. If that changes anywhere, those change will be pushed to client and that would update in real time. This is our first step towards implementing WebSockets and also doing it in an MVC fashion, so that we can make sure performance is on par and it's the scalable solution before we update the rest of the sidebar to make it real time and then move to issue boards.

A

Big thing we'll be focusing on with as resources the Jura importer NBC, and this one is pretty straightforward for the NBC users will be able to import their issues from JIRA with their titles, with the description and with some other basic fields, but we're not going to be doing user mapping and then you see that will come in a follow on we're. Making pretty good progress on this and I. Don't have any concerns about shipping in 12.10 and that's it for the project management group within the planet stage. Thanks.