Skip to content

Adding Community Program workflows to L&R workflows

Tom McAtee requested to merge lnr/workflows/community-programs into master

Why is this change being made?

Many workflows relating to customers of our community programs are not documented, and generally SEs raise tickets in #Community-Programs for advice (delaying ticket resolutions for SEs and adding to the workloads of the Community Programs team).

The proposed additional workflows include:

  • Handling product transfer requests
  • Adding program-specific contact information to the workflow
  • Handling enquiries about true-ups for community programs
  • Handling invalid coupons
  • Handling SheerID enquiries

The proposed formatting changes include:

  • Moving application and renewal workflows for each Program type from individual workflow sections, to subsections under a "Applications and Renewals" section.

Apologies for not breaking this into multiple MRs/commits, I'm still adjusting to the Web IDE 😅

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 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