updating the issue template - bug report
This commit is contained in:
parent
2716202cdc
commit
f25cee8616
1 changed files with 52 additions and 22 deletions
74
.github/ISSUE_TEMPLATE/bug_report.md
vendored
74
.github/ISSUE_TEMPLATE/bug_report.md
vendored
|
|
@ -6,33 +6,63 @@ labels: ''
|
||||||
assignees: ''
|
assignees: ''
|
||||||
|
|
||||||
---
|
---
|
||||||
|
**Instructions**
|
||||||
|
Please include a detailed Title above. Next, please complete the following sections below:
|
||||||
|
* Bug Description
|
||||||
|
* Impacts
|
||||||
|
* Steps To Reproduce
|
||||||
|
* Expected Behavior
|
||||||
|
* Screenshots (optional)
|
||||||
|
* Host Environment (optional)
|
||||||
|
* Additional Context (optional)
|
||||||
|
|
||||||
**Describe the bug**
|
Finally, press the 'Submit new issue' button. The Core Team will evaluate and prioritize your Bug Report for future development.
|
||||||
|
|
||||||
|
**Bug Description**
|
||||||
A clear and concise description of what the bug is.
|
A clear and concise description of what the bug is.
|
||||||
|
|
||||||
**To Reproduce**
|
**Impacts**
|
||||||
Steps to reproduce the behavior:
|
Describe which portion(s) of Peerplays may be impacted by this bug. Please tick at least one box.
|
||||||
1. Go to '...'
|
- [ ] API (the application programming interface)
|
||||||
2. Click on '....'
|
- [ ] Build (the build process or something prior to compiled code)
|
||||||
3. Scroll down to '....'
|
- [ ] CLI (the command line wallet)
|
||||||
4. See error
|
- [ ] Deployment (the deployment process after building such as Docker, Gitlab, etc.)
|
||||||
|
- [ ] P2P (the peer-to-peer network for transaction/block propagation)
|
||||||
|
- [ ] Performance (system or user efficiency, etc.)
|
||||||
|
- [ ] Protocol (the blockchain logic, consensus, validation, etc.)
|
||||||
|
- [ ] Security (the security of system or user data, etc.)
|
||||||
|
- [ ] UX (the User Experience)
|
||||||
|
- [ ] Other (please add below)
|
||||||
|
|
||||||
**Expected behavior**
|
**Steps To Reproduce**
|
||||||
|
Steps to reproduce the behavior (example outlined below):
|
||||||
|
1. Execute API call '...'
|
||||||
|
2. Using JSON payload '...'
|
||||||
|
3. Received response '...'
|
||||||
|
4. See error in screenshot
|
||||||
|
|
||||||
|
**Expected Behavior**
|
||||||
A clear and concise description of what you expected to happen.
|
A clear and concise description of what you expected to happen.
|
||||||
|
|
||||||
**Screenshots**
|
**Screenshots (optional)**
|
||||||
If applicable, add screenshots to help explain your problem.
|
If applicable, add screenshots to help explain process flow and behavior.
|
||||||
|
|
||||||
**Desktop (please complete the following information):**
|
**Host Environment**
|
||||||
- OS: [e.g. iOS]
|
Please provide details about the host environment. Much of this information can be found running: `witness_node --version`.
|
||||||
- Browser [e.g. chrome, safari]
|
- Host OS: [e.g. Ubuntu 18.04 LTS]
|
||||||
- Version [e.g. 22]
|
- Host Physical RAM [e.g. 4GB]
|
||||||
|
- Peerplays Version
|
||||||
**Smartphone (please complete the following information):**
|
- OpenSSL Version: [e.g. 1.1.0g]
|
||||||
- Device: [e.g. iPhone6]
|
- Boost Version: [e.g. 1.67.0]
|
||||||
- OS: [e.g. iOS8.1]
|
|
||||||
- Browser [e.g. stock browser, safari]
|
**Additional Context (optional)**
|
||||||
- Version [e.g. 22]
|
|
||||||
|
|
||||||
**Additional context**
|
|
||||||
Add any other context about the problem here.
|
Add any other context about the problem here.
|
||||||
|
|
||||||
|
## PBSA / Developer tasks
|
||||||
|
|
||||||
|
- [ ] Evaluate / Prioritize Bug Report
|
||||||
|
- [ ] Refine User Stories / Requirements
|
||||||
|
- [ ] Define Test Cases
|
||||||
|
- [ ] Design / Develop Solution
|
||||||
|
- [ ] Perform QA/Testing
|
||||||
|
- [ ] Update Documentation
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue