Skip to content

Update Post-call macro title

Kent Japhet Ballon requested to merge kballon-main-patch-79389 into main

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

We observed that the macro title used in the Customer Emergencies workflow has been updated. This MR aims to update the title for consistency.

The changes were brought about by this commit. We plan to update Support::Self-Managed::Post Customer Call to Support::Customer Calls::Call Completed - Summary

Discussion in slack:

Rebecca S
  19 hours ago
It may have been renamed/consolidated as part of the recent work creating an entirely new call-workflow — with various fields and checkboxes. I think that not everyone is using that new mechanism, but many people have used the Post Call macro for a long time.


Alyssa Villa
  19 hours ago
That macro is now called Support::Customer Calls::Call Completed - Summary  like what Alex said. See https://gitlab.com/gitlab-com/support/support-ops/zendesk-global/macros/-/merge_requests/566#note_1376964763 for more context. We should probably update the doc to link the correct macro to use.

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

Merge request reports