Browse code

issues: re-order issue template for more clarity

Triaging issues has become a little challenging since the meat
of the information is below a large amount of unstructured
command line output. These changes add a description and move
the reproduction and expected/received results above the
unstructured output.

This should help for initial triaging, as well as self-triaging.

Signed-off-by: Stephen J Day <stephen.day@docker.com>

Stephen Day authored on 2016/09/13 06:30:24
Showing 1 changed files
... ...
@@ -19,29 +19,17 @@ Use the commands below to provide key information from your environment:
19 19
 You do NOT have to include this information if this is a FEATURE REQUEST
20 20
 -->
21 21
 
22
-**Output of `docker version`:**
23
-
24
-```
25
-(paste your output here)
26
-```
27
-
28
-
29
-**Output of `docker info`:**
30
-
31
-```
32
-(paste your output here)
33
-```
34
-
35
-**Additional environment details (AWS, VirtualBox, physical, etc.):**
36
-
22
+**Description**
37 23
 
24
+<!--
25
+Briefly describe the problem your having in a few paragraphs.
26
+-->
38 27
 
39 28
 **Steps to reproduce the issue:**
40 29
 1.
41 30
 2.
42 31
 3.
43 32
 
44
-
45 33
 **Describe the results you received:**
46 34
 
47 35
 
... ...
@@ -49,3 +37,17 @@ You do NOT have to include this information if this is a FEATURE REQUEST
49 49
 
50 50
 
51 51
 **Additional information you deem important (e.g. issue happens only occasionally):**
52
+
53
+**Output of `docker version`:**
54
+
55
+```
56
+(paste your output here)
57
+```
58
+
59
+**Output of `docker info`:**
60
+
61
+```
62
+(paste your output here)
63
+```
64
+
65
+**Additional environment details (AWS, VirtualBox, physical, etc.):**