Skip to content

MktgOps handbook MR: 20230918 - 20230929

Jameson Burton requested to merge jburton-master-patch-85359 into master

Why is this change being made?

  1. Update made to the cancellation assets set up description @jburton
  2. Campaign updates !129580 (comment 1564009363) @stran5
  3. Updates Sales systems process @amy.waller
  4. Mops issue template updates https://gitlab.com/gitlab-com/marketing/marketing-operations/-/merge_requests/143
  5. Removed Drift Page @emathis
  6. Removed older pages @amy.waller
  7. Removed under construction message from 6sense page - @nikkiroth
  8. Scoring cleanups @amy.waller
  9. Tool eval update https://gitlab.com/gitlab-com/marketing/marketing-operations/-/merge_requests/144 - @degan and @nikkiroth
  10. Added instructions to set a Delegated approver for the MDF approval process @stran5
  11. Create SFDC to sync to Vartopia @stran5
  12. How to prevent clean up job from reassigning leads to Inquiry Queue @stran5
  13. Update Marketing Ops learn hot topic section @stran5
  14. Adds FM 6sense training recordings to 6sense page - @nikkiroth
  15. Update landing page naming convention @jennyt

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • 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
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
Edited by Jenny Tiemann

Merge request reports