The preferred method for providing customer feedback on issues is to use an **internal comment** with the [Customer Issues Prioritization Framework](/handbook/product/product-processes/customer-issues-prioritization-framework/#quick-start). Internal comments protect customer privacy and prevent sensitive business information from being publicly visible.
**When a public comment is necessary** (such as in Support workflows where the customer expects to see the comment), use the template below. You can copy/paste this to make sure you don't miss anything or [create a comment template](https://docs.gitlab.com/user/profile/comment_templates/#create-comment-templates) for reusability. Modify the template as necessary for bug issues.
```markdown
<!-- Select the appropriate subscription and product text below and remove the others (note: do not add them as labels)>
The following ~customer is interested in this capability
- Subscription: ~"GitLab Ultimate" OR ~"GitLab Premium" OR ~"GitLab Free"
- Product: ~"self-managed" OR ~"gitlab.com" OR ~"GitLab Dedicated"
- Link to request:
- Customer Priority: [low/medium/high]
- Use case: [why interested, problem to solve, current workaround, impact]
The preferred method for providing customer feedback on issues is to use an **internal comment** following the process [described below](#quick-start). Internal comments protect customer privacy and prevent sensitive business information from being publicly visible.
If a **public comment is necessary** (such as in Support workflows where the customer expects to see the comment), use the [Feedback template](/handbook/product/product-management/#feedback-template) instead.
## Quick Start
To prioritize a customer issue, add an **internal note** comment to the issue with the
appropriate label and context. Internal notes are made availble only to GitLab Team Members
appropriate label and context. Internal notes are made available only to GitLab Team Members
and help ensure customer sentiment is not unnecessarily exposed.
