Update the issue template to reduce clutter

Lots of issues filed didnt take the time to remove the boilerplate
text and give the details needed. This format mimics the update to
pull requests but inverts type and description.
pull/6728/head
Sam Grove 2018-04-19 17:09:13 -05:00 committed by Martin Kojtal
parent b033a6e42e
commit 27f2789b3f
1 changed files with 25 additions and 46 deletions

View File

@ -1,48 +1,27 @@
Note: This is just a template, so feel free to use/remove the unnecessary things
### Issue request type
<!--
Required
Please add only one X to one of the following types. Do not fill multiple types (split the pull request otherwise) or
change the layout.
[X] Question
[ ] Enhancement
[ ] Bug
-->
[ ] Question
[ ] Enhancement
[ ] Bug
<!--
Required
Add detailed description of what is being reported
Good example: https://os.mbed.com/docs/latest/reference/workflow.html
Things to consider sharing:
- What target does this relate to?
- What toolchain is being used?
- What is the SHA of Mbed OS (git log -n1 --oneline)?
- Steps to reproduce (Did you publish code or a test case that exhibits the problem)
-->
### Description
- Type: Bug | Enhancement | Question
- Related issue: `#abc`
- Priority: Blocker | Major | Minor
---------------------------------------------------------------
## Bug
**Target**
K64F|??
**Toolchain:**
GCC_ARM|ARM|IAR
**Toolchain version:**
**mbed-cli version:**
(`mbed --version`)
**mbed-os sha:**
(`git log -n1 --oneline`)
**DAPLink version:**
**Expected behavior**
**Actual behavior**
**Steps to reproduce**
----------------------------------------------------------------
## Enhancement
**Reason to enhance or problem with existing solution**
**Suggested enhancement**
**Pros**
**Cons**
-----------------------------------------------------------------
## Question
**How to?**