-
Notifications
You must be signed in to change notification settings - Fork 116
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
chore: add yaml issue template #1338
Conversation
- To get detailed info on bugs
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.
Overall, I really like the "form" style that you are introducing here! Especially inserting the codeblock automatically that customers can just paste their code in will be nice, because customers often fail to do that on their own. This should certainly reduce the friction for customers a little bit.
The goal of the template should be to minimize the number of follow up questions that we need to ask the customer, but we also don't want to collect info that isn't usually relevant, since it will increase the length of the issue, and thus the time that it takes to triage issues during sprint planning or during on call. I suggested a couple ways to simplify / reduce the number of questions asked.
remove redundant questions Co-authored-by: Richard McClellan <[email protected]>
Co-authored-by: Richard McClellan <[email protected]>
These two questions are asked on our existing bug template, and do sometimes result in useful context, so we should add them to this one:
Also, as a part of this PR, please remove the old bug template, since we only need one. |
Old template not required.
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.
🚀
create new yaml issue template to get detailed info on bugs.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.