expand the issue template and remove the severity field
* 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 <steven@stebalien.com>
Steven Allen committed
Jan 29, 2018 at 15:29 UTC
3d4da02a2ecc84261a5cdffaefc2508eae6315d4
1 file changed
+23
-18
ISSUE_TEMPLATE.md
+23
-18
@@ -1,33 +1,38 @@
1
<!--
2
+Welcome to the go-ipfs bug tracker. This is for you! Please read, and then delete this text before posting it.
3
+
4
+If you haven't yet searched the issue tracker for an existing report concerning your issue, please do so now.
5
+
6
+The go-ipfs issues are only for bug reports and directly actionable feature requests. Read https://github.com/ipfs/community/blob/master/contributing.md#reporting-issues if your issue doesn't fit either of those categories.
7
+
8
+If you have a *SUPPORT QUESTION*, please direct it to our forum at https://discuss.ipfs.io.
9
+
10
+Read https://github.com/ipfs/go-ipfs/blob/master/docs/github-issue-guide.md if you are not sure how to fill in this issue.
11
+-->
12
+
13
+#### Version information:
14
+<!--
15
Output From `ipfs version --all`
16
17
If your version is older than *0.4.11* please update
18
and re-check if the problem persists.
19
-->
7
-#### Version information:
20
9
-<!-- Bug, Feature, Enhancement, Etc -->
21
#### Type:
11
-
12
-<!-- One of following:
13
- Critical - System crash, application panic.
14
- High - The main functionality of the application does not work, API breakage, repo format breakage, etc.
15
- Medium - A non-essential functionality does not work, performance issues, etc.
16
- Low - An optional functionality does not work.
17
- Very Low - Translation or documentation mistake. Something that really does not matter much but should be noticed for a future release. -->
18
-#### Severity:
22
+<!-- Bug, Feature, Enhancement, Etc -->
23
24
#### Description:
25
+<!--
26
+This is where you get to tell us what went wrong or what feature you need. When doing so, please make sure to include *all* relavent information.
27
28
+When requesting a feature, please be sure to include:
29
30
+* Your motivation. Why do you need the feature?
31
+* How the feature should work.
32
33
+When reporting a bug, please try to include:
34
25
-
26
-
27
-
28
-<!--
29
-This is for you! Please read, and then delete this text before posting it.
30
-The go-ipfs issues are only for bug reports and directly actionable features.
31
-Read https://github.com/ipfs/community/blob/master/contributing.md#reporting-issues if your issue doesn't fit either of those categories.
32
-Read https://github.com/ipfs/go-ipfs/blob/master/docs/github-issue-guide.md if you are not sure how to fill in this issue.
35
+* What you were doing when you experienced the bug.
36
+* Any error messages you saw, *where* you saw them, and what you believe may have caused them (if you have any ideas).
37
+* When possible, steps to reliably produce the bug.
38
-->