-
Notifications
You must be signed in to change notification settings - Fork 255
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 Issue templates and Error Reporting flows #1165
Comments
Sample issue: WordPress user has installed a plugin and something weird is happening Suggested workflow: Provide steps to troubleshoot origination of issue, offer help with searching this repo for relevant discussions. If troubleshooting doesn't work, and issue hasn't been discussed, open ticket Issue sampleerror may be because of a plugin Troubleshooting steps
etc. Direct the user on how to troubleshoot first, before opening up an Issue |
+1 to this ❤️ |
@adamziel - I'll start working on "canned responses" to issues if you will, ie:
via #1180 (comment) |
User issue onboardingWhat version of Playground are you running?
Issue triageRoute to various issue templates with known limitations, best practices for troubleshooting, etc These templates can be created by looking at previously resolved issues and re-creating those journeys. |
|
How about starting with a few common templates adapted from these team repos? |
Thank you for linking these issue templates @ironnysh! The Gutenberg repo has some of the best "issue onboarding" examples and the others probably have great context, too. I will print all of these templates out and search for common ground with the Playground. |
re: including
From WordPress security folks |
This totally didn't work BTW 😢 - I'm old school and like to print stuff to mark-up. :) Marked as high priority, this totally needs to be done before the contributor day. |
PR to include an Issue template for online version of the playground IE: playground.wordpress.net PR for an issue template for |
Both PRs have been updated- please review at your convenience, @adamziel |
Issue templates allow repository owners to provide guard rails when submitting a new issue to a repo.
Is the issue a feature request? Perceived bug? General question about architecture..?
Setting up templates for when a user clicks
New Issue
could be invaluable for saving time and offering troubleshooting steps up front. If the user is unable to find relevant information, issue templates can guide the user how to best submit a request.When going through the issue template flow, labels can be automatically assigned to the issue to provide better filtering.
Sample issue templates
From the Documentation Issue Tracker
Resources
Configuring issue templates in GitHub repositories
Issue templates for Gutenberg
The text was updated successfully, but these errors were encountered: