Skip to content

17.11 Foundations:Import and Integrate Planning

Team

groupimport and integrate

Capacity / OOO

Team Weight
backend 43
frontend 14

Anticipated % split for features/bugs/maintenance

  • 40% features (weight)
  • 30% bugs (weight)
  • 30% maintenance (weight)

Board

High level Objectives / Progress on quarterly OKRs

In this and following milestones, we focus on bringing Direct transfer to GA. This is crucial as many customers avoid beta products due to internal policies and reliability concerns - GA status provides the assurance they need while delivering a smoother experience. Within this effort in the current milestone we will improve on the new user contribution mapping experience, in particular work on contribution mapping of banned, blocked, deleted, ghost users - epic User contribution mapping of banned, blocked, d... (gitlab-org&16106). We will also improve on reassignment experience when on .com, by showing only Enterprise users for the groups this feature is enabled for -Direct-transfer placeholder users: list Enterpr... (gitlab-org/gitlab#510673 - closed).

Objectives

Product prioritized typefeature list

  1. Any %"17.x" carryover
    1. Not started
      • item
    2. At risk of slipping
  2. New feature work

Engineering prioritized typemaintenance list

  1. Any %"17.x" carryover
    1. Not started
    1. At risk of slipping
    • item
  2. New maintenance work

Prioritized typebug list

  1. Any %"17.x" carryover
    1. Not started
    • item
    1. At risk of slipping
  2. New bugs

Release Post Items

Status Issue Release Post MR

TODO

  • Write milestone objectives.
  • Discuss capacity (OOO plans).
  • Review the roadmap and milestone objectives with the team.
  • Issues that can be delivered in 17.x, label with priority label ~"milestone::x" and set milestone to 17.x.
  • Publish the planning call video. Group playlist.
  • Link planning issue for the next milestone to this one.

< Previous | Next >

Edited by Martin Wortschack