Fulfillment Recap: 16.10
❓ What This Is
Fulfillment work is largely cross-functional and impacts many teams at GitLab. This milestone review is aimed at sharing with our cross-functional stakeholders the progress made in the most recent milestone, share some wins, acknowledge challenges, and reflect on key learnings as we move into the following month.
Group Updates
Provision
Key achievements:
- Successful launch of <strong data-sourcepos="11:26-11:55">GitLab Duo Pro beta cutoff</strong>, transitioning all customers to a paid add-on on
2024-02-15
🎉 Alongside the Duo launch, we also:- Provisioned Duo Pro access for GitLab team members in our top level groups and enabled easy assignment of team members by extending the bulk assignment script to GitLab.com,
- Updated UI references and the plan name from
Duo Pro
to the legal-approvedGitLab Duo Pro
, - Tested a new process for allowing 1-year co-terming of Duo Pro,
- & completed a detailed work break down for an initial iteration of bulk assignment and made progress on initial selection abilities and a bulk action confirmation modal.
- This milestone we also began work to introduce a new customer trial for GitLab Duo Pro, with launches now targeting next week.
-
For Duo Pro trials for GitLab.com, we went from
10%
completion to100%
dev complete within the milestone by completing work such as: - For Duo Pro trials for Self Managed & Dedicated, we scoped out a first iteration that allows us to use cloud licensing and moved to
50%
dev completion with:
-
For Duo Pro trials for GitLab.com, we went from
Team updates:
Learnings:
- In the spirit of
& , check out some learnings from this launch in the Duo Pro launch retrospective.
Utilization
Key achievements:
- Closed this epic SaaS User Caps Pending Member Notification & Pa... (gitlab-org&12463 - closed), which simultaneously improved our error budget and enhanced our user caps functionality by auto-approving members in approval queue for certain circumstances.
- Continued development of Block seat overages including:
- Completing our initial spike & creating a demo
- Completed preventing members from being added beyond what purchased seats are available, which is probably one of the most key (possibly one of the most challenging) backend issues given it is the actually blocking of member additions when seats are not available.
- Designs defined & FE implementation started for https://gitlab.com/gitlab-org/gitlab/-/issues/441796+s, which will notify the owner of the namespace via e-mail when someone tries to add members but no seats are available.
- Cells work, which has been a Fulfillment wide effort:
- The first discovery phase for efforts needed for fulfillment owned features to be compatible with Cells architecture has been completed.
- We have identified and evaluated all general flows for possible integration issues that may arise with the Cells architecture integration.
- Next steps are to continue to determine our iteration and end state plan, which is being discussed here.
Team updates:
Learnings:
- Running into some challenges with managing promotion of guest users on Ultimate. Pending promotion can happen to non-members and such promotion requests don't have a relevant member entry, which makes it challenging to display on the
/members
page since that code is heavily focused on displaying particularly members. We had to detach Promotion Requests from Members table, and thus have a breakout in/members
page code to display non-members entities.
Subscription Management
Key achievements:
- Completed https://gitlab.com/groups/gitlab-org/-/epics/10670+
🎉 . Keeping the epic open for monitoring. - Great progress on https://gitlab.com/groups/gitlab-org/-/epics/10688+. We are at ~50% completion.
- Fixed a bug Assigned Support Engineer SKU is not showing as... (gitlab-org/customers-gitlab-com#8395 - closed).
- Fixed a bug https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/5704+.
- Made a few usability improvements:
- Completed UX and engineering breakdown for project Ramon.
Team updates:
Learnings:
Fulfillment Platform
Key achievements:
- Completed a Rake task than helped unlink multiple CDot user accounts driving us closer to achieve 1-1 Gitlab account & Cdot user login goal
- Subsequently improved the error messaging to indicate inability to link a Gitlab.com account (since its already linked) with actionable feedback to contact support
- Completed Zuora objects update required to complete phase 1 of New order flow of AWS marketplace public offer
- Delivered a blue print of improved approach to plan & SKU management marking the completion of OKR
- Completed Renaming & moving of Zuora namespaces [epic] as preparatory work to free up namespace required for Zuora Cache model
- Address all changes required to address new Zuora API limit enforcement in sandbox and developer to avoid testing/investigation disruption
- Completed https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/8082+ to enable showing of clear causes of error when the user attempts a namespace transfer
Learnings
Tasks
-
@ofernandez2
update issue title & milestone to reflect the appropriate milestone -
@ofernandez2
create a retro thread for feedback. -
@ofernandez2
set a due date for the issue. -
All PMs add updates for their groups -
Provision - @courtmeddaugh -
Subscription Management - @tgolubeva -
Utilization - @alex_martin -
Fulfillment Platform - @ppalanikumar
-
-
Make template updates based on any retro/feedback items. https://gitlab.com/gitlab-com/Product/-/blob/main/.gitlab/issue_templates/Fulfillment-Monthly-Recap.md -
@ofernandez2
add a highlights comment and close out the issue. Tag in interested parties:cc: @justinfarris @s_mccauley @jrabbits @james_harrison @gitlab-org/fulfillment @gitlab-com/support/licensing-subscription @kkutob @NabithaRao @mikesmith1 @achampagne1 @caroline.swanson @natalie.pinto @cnodari @brianmwong @broncato @nscala @lwhelihan @sheelaviswanathan
Edited by Omar Fernandez