Skip to content

17.10 Foundations:Import and Integrate Planning

Team

groupimport and integrate

Capacity / OOO

Team Weight
backend 45
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 milestone we plan to extend user contribution mapping importers feature by allowing to re-assign contributions by submitting a CSV file. That will benefit especially large customers with many users, allowing for faster reassingment of contributions after an import.

Next, we want to provide prompt feedback to reassigning user when users belong to groups enforcing SAML. If groups have SAML SSO set up, the accounts on Gitlab.com need to be verified and linked to the group's SAML SSO before reassignment to their Placeholders. If this is not done, membership validation will fail and membership relations will not be created correctly on Gitlab.com. Currently, owners can choose unverified users and we don't show anything in the UI when owner tries to reassign to unverified user.

Finally, we want to complete the work started by a community contributor and allow all webhooks to self-heal, keeping users workflow automation running smoothly without interruption. Related blog post.

Objectives

Product prioritized typefeature list

  1. Any %17.9 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
    1. At risk of slipping
    • item
  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