Skip to content

Remove internal note hints from feedback template

Manuel Grabowski requested to merge mg-publicfeedback-20230403 into master

Why is this change being made?

I'm raising this MR to continue the discussion I tried starting on the original MR that added the guidance to post these comments as internal notes, see here: !116454 (comment 1228821788)

As I mentioned there, it's a vital part of the Support process to post these comments publicly and link our customers back to them.

Additionally it seems that the main (only?) reason for suggesting to add these as internal comments was concerns over sharing the number of seats publicly (as per this comment), but the current version of the template doesn't include that information anymore anyway.

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.

Merge request reports

Loading