Removes specialized forms and redirects partners to use named contacts and normal forms
Why is this change being made?
As a part of improving support for the customers of partners, we're allowing customers to open tickets directly with GitLab support and requiring they be informed and active in choosing to include partners in their support interactions.
This MR updates guidance for how partners can open tickets. The main effect is on Open partners who can:
- open tickets for their customers
- must direct their customers to include them if they wish to be included
Once accomplished, the specialized forms for both types of partners will be removed.
Relates to:
- https://gitlab.com/gitlab-com/support/support-ops/support-ops-project/-/issues/890
- https://gitlab.com/gitlab-com/support/support-team-meta/-/issues/5026
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, and the content is SAFE
-
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
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
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.