expand the issue template and remove the severity field #4624
Conversation
Stebalien
commented
Jan 29, 2018
Stebalien
commented
- Direct users seeking support to the forums.
- Remove the severity field. It doesn't actually help (especially because we can't filter by it and, anyways, we end up deciding the severity).
- Put the section comments inside the sections. This has been annoying me from day 1.
- Put the welcome text at the top so users actually read it.
- Expand on what we want in a description.
* Direct users seeking support to the forums. * Remove the severity field. It doesn't actually help (especially because we can't filter by it and, anyways, *we* end up deciding the severity). * Put the section comments *inside* the sections. This has been annoying me from day 1. * Put the welcome text *at the top* so users actually read it. * Expand on what we want in a description. License: MIT Signed-off-by: Steven Allen <[email protected]>
ghost
assigned 
I've literally never found it useful (not even for the entertainment value). From reading the issue, I can tell how sever it is. Without reading the issue, I can't trust the severity field. IMO, severity is better handled through labels anyways (searchable, easy to see, not set by the reporter). I wonder if it's possible to give labeling permission to contributors. (Although I may just be getting curmudgeonly) |
I agree. Not sure about the possibility of giving labeling permission to contributors. |
Fine grained permissions? GitHub? Silly me. We'd have to use a bot. |
|
jenkins fails for some reason? Want to file that as an issue? |
|
Since we decided to remove the Severity field we also need to fix https://github.com/ipfs/go-ipfs/blob/master/docs/github-issue-guide.md so it doesn't mention the Severity field. |
|
@whyrusleeping standard "timed out waiting for api file show up" bug. |
|
@Stebalien that generally means that the daemon failed to start for some reason. Not a good sign |
|
@whyrusleeping unfortunately, it's a common race condition in our tests. Daemon takes too long to start (over 5 seconds). There may be some underlying cause bit I have no idea what it is; I've never reproduced this locally. |
|
Annoying, but alright. |
