Create issue template #6
Merged
Conversation
This file contains 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
|
👏👏✍️✍️👏👏 |
|
After discussing with @Jenneh in meeting, we're going to merge and try this out. We can always make changes if needed. Thanks! |
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.
Since we will be regularly creating issues with feedback from user testing @Jenneh requested that at least she and I have a common ground for what to provide in issues and how to structure them. This is a plain template for what I think make clear and closable issues (because of the
## Acceptance criteriasection) based on my past experience, but it's certainly not the only way to do this.@Jenneh I've requested your review because I believe we will be the ones using this most frequently. As always, anyone else is welcome to weigh in, too! Thanks! 🌻
Edit: you can find an example of this template in use at #5 if that is helpful.