Skip to content

Adding a note to the 'contact change' process for reseller customers

Why is this change being made?

This change is being made as the current workflow does not detail the edge case where a customer requesting a contact change has purchased their subscription via a reseller.

I have added:

  1. Some steps detailing which records need to be changed and by whom (specifically: the support and billing teams)
  2. An extra note to assist when such a client requests multiple contacts are added to their account

Author Checklist

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Edited by Tom McAtee

Merge request reports

Loading