Creating/adding to issues and feature requests
Recently, @JobV gave a great sales enablement talk on giving feedback to product management, which I though was very relevant to our team as well. I've compiled some notes and links below from that talk, slack conversations, and other discussions.
When creating issues, please use the appropriate template (make sure to include version number even on .com)
and labels, particularly:
- Type: add
customer
if applicable (bug and feature proposal will be added as part of the template) - Subject: optional but helpful
- Team/stage: very important! you otherwise might not get visibility on the issue
- priority/severity: technically optional, but very helpful, especially severity. If something is P1/S1, consider posting it in the appropriate slack channel and mentioning the PM as well.
- regression?: mark with appropriate regression labels
- on .com?: use the
Reproduced on GitLab.com
label
Refer to the product categories to see which team/stage to label, or if you find a similar recent issue, use the same labels.
For existing issues and feature proposals, consider using the feedback template or including similar information (not just a link).
I imagine the issue escalation workflow is the best place to put this information, which we might also rename to Creating and Escalation Issues
I'll work on a MR but if anyone has input on information to add, please do!