Skip to content

17.7 Foundations:Import and Integrate Planning

Team

groupimport and integrate

Capacity / OOO

Team Weight
backend 40
frontend 12

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 milestone we will work on items from User Contribution Mapping - post first release (gitlab-org&14774). Improved user contribution mapping remains the top-priority for 17.7 as well. This feature enhances the user experience, requiring less preparation before the migration and enabling mapping contributions and memberships of users with different emails on the source and destination instances. It makes the import more transparent to all participants, as users need to accept mapping request. Documentation is available for review.

In 17.7 we plan to:

  • Complete integrating this feature with 3rd party importers.
  • Adding CSV.

In this milestone we also continue working towards Cells 1.0.

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
  2. New maintenance work

Prioritized typebug list

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

Release Post Items

Status Issue Release Post MR

TODO

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

< Previous | Next >

Edited by Martin Wortschack