# Developer Experience Request ## Summary <!--Provide a brief summary of the issue you're experiencing--> This ask is aiming to evaluate comments through an automate triage process in an effort to improve Field Feedback to Product while also decreasing chances of PII data from being leaked through public issues. Create a comment processor that enforces required labels on comments containing Salesforce or Zendesk links within gitlab-org projects. ##### Use Case 1: Enforce Required Labels When a comment in a gitlab-org project includes a Salesforce or Zendesk link (gitlab.my.salesforce.com, gitlab.lightning.force.com, gitlab-federal-support.zendesk.com, gitlab.zendesk.com), the processor should: 1. Detect the presence of one of the following labels in the **comment body** (not the issue/MR itself) - these labels still need to be created: * `~Ultimate::Blocker` * `~Premium::Blocker` * `~DAP::Blocker` * `~Ultimate::Retention` * `~Premium::Retention` * `~DAP::Retention` * `~Ultimate::Fast Follow` * `~Premium::Fast Follow` * `~DAP::Fast Follow` * **Net New Below as of 2026-01-22** * `~Dedicated::Blocker` * `~Dedicated::Retention` * `~Dedicated::Fast Follow` 2. If none of these labels are present in the comment body, post a response comment requesting that one be added ##### Use Case 2: Enforce Internal Notes Provide a response to the comment (with a SFDC/ZenDesk link in it) when it is not marked as an internal note https://docs.gitlab.com/user/discussions/#add-an-internal-note. Related MR: https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/17723+ ## Requester Information <!--Fill out your details below--> * **Name: Tim Poffenbarger** * **Team: Solution Architecture** * **Role: Sr Director** * **GitLab Handle: `@poffey21`** ## Request Details * **Urgency: Medium** <!--Critical/High/Medium/Low--> * **Requested Completion Date:** <!--YYYY-MM-DD--> * **Is this blocking any release or milestone?** <!--Yes/No - If yes, provide details--> <!--Do not edit below this line-->