-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create support ticket template #1749
Conversation
- type: checkboxes | ||
attributes: | ||
label: Boost component | ||
description: Please select the boost component you are filing a bug for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just so I understand, what is the rationale for having this option at all?
It will take very little time for us to label it once the issue is captured, not having it would reduce the barrier for capturing an issue, and we need to read through the issue to check it's labeled right in any case. No?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are multiple way to creating a support ticket. But, generally agreed upon industry standard is to collect some basic information to allow support engineers to provide an initial direction of investigation rather than asking same questions from the client/customer.
If we don't even collect which component would is impacted, then this template would be no different than slack conversations.
PS: There labels are not github labels.
@LexLuthr lgtm |
If the template looks good, please feel free to merge it