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>
This commit is contained in:
Stephen Day 2016-09-12 14:30:24 -07:00 committed by Stephen J Day
parent 6edf09cf58
commit be3bc483c6
No known key found for this signature in database
GPG key ID: FB5F6B2905D7ECF3

View file

@ -19,29 +19,17 @@ Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST You do NOT have to include this information if this is a FEATURE REQUEST
--> -->
**Output of `docker version`:** **Description**
```
(paste your output here)
```
**Output of `docker info`:**
```
(paste your output here)
```
**Additional environment details (AWS, VirtualBox, physical, etc.):**
<!--
Briefly describe the problem your having in a few paragraphs.
-->
**Steps to reproduce the issue:** **Steps to reproduce the issue:**
1. 1.
2. 2.
3. 3.
**Describe the results you received:** **Describe the results you received:**
@ -49,3 +37,17 @@ You do NOT have to include this information if this is a FEATURE REQUEST
**Additional information you deem important (e.g. issue happens only occasionally):** **Additional information you deem important (e.g. issue happens only occasionally):**
**Output of `docker version`:**
```
(paste your output here)
```
**Output of `docker info`:**
```
(paste your output here)
```
**Additional environment details (AWS, VirtualBox, physical, etc.):**