New issue templates! #3400
Merged
New issue templates! #3400
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Laren-AWS
requested changes
Aug 2, 2022
ford-at-aws
force-pushed
the
new-template
branch
from
16c7ee7 to
d43cd33
Compare
Laren-AWS
reviewed
Aug 2, 2022
Laren-AWS
previously requested changes
Aug 2, 2022
scmacdon
approved these changes
Aug 3, 2022
|
UPDATE: I ended up deleting the |
ford-at-aws
force-pushed
the
new-template
branch
from
70c70c5 to
5d24fb4
Compare
Laren-AWS
approved these changes
Aug 3, 2022
ford-at-aws
force-pushed
the
new-template
branch
from
614496d to
c7600f7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
story link: #3295
context
Our team triages and actions issues created internally and externally; however, we feel that the current templates are outdated, bloated, and missing key details.
While we work out an "Life of an Issue" playbook (similar to the Life of a PR), it would really help to feel confident in the existing templates, which we lean on as a tool for user input and story creation.
data/anecdotes
Most issues created are for/by our team. Very few were created externally. See this table, which was pulled using this custom Python script that I wrote:
This image shows that most issues are created by our team:
This image shows that most issues are not created using a template.
Conclusion: MOST of our issues are created internally (likely via the Zenhub portal) and do NOT use templates (meaning that either the templates are poor AND/OR they "easy" workflow for creating issues doesn't allow for templates).
the user story
As a code examples engineer, I want a new set of issue templates to:
what's in this PR?
This PR:
testing
This was tested in my fork. Please see https://github.com/ford-at-aws/aws-doc-sdk-examples/issues/new/choose.
risk
This is a low-risk change that can easily be reverted in minutes without any impact to data or customer experience. The biggest risk is the possibility that this will create external friction that is invisible to our team.
notes for the reviewer
I expect there to be some comments on this, so please fire away! I'm happy to make any changes that add value.