-
Notifications
You must be signed in to change notification settings - Fork 1
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
Just leaving a single bug template instead of the existing three one #3378
Conversation
@jpellizzari this is the minimal template that I suggest we could use. |
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.
Definitely...asking people to figure out at what stage the bug was introduced didn't help.
0405fc3
to
3ccd03d
Compare
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.
As discussed elsewhere, I support this simplification 👍
3ccd03d
to
9b85250
Compare
Part of https://www.notion.so/weaveworks/Should-we-bring-back-bug-template-7ed35726574846cea26d1d398487519d?pvs=4
What changed?
Replacing existing three bug templates for a single one.
Drafts it for further discussion.
Why was this change made?
Given the problem, we have more folks going into the blank issue for reporting bug that using a template. the hypothesis is that people is not clearly able to determine which of the three to select therefore selects a blank one. if that is the case, we are losing scope information.
With a single template we expect to improve this situation: