Files
kami-parse-server/.github/ISSUE_TEMPLATE.md
Benjamin Wilson Friedman 9145c88562 Corrected outdated links (#4254)
2017-10-12 22:40:47 -04:00

44 lines
1.4 KiB
Markdown

We use GitHub Issues for bugs.
If you have a non-bug question, ask on Stack Overflow or Server Fault:
- https://stackoverflow.com/questions/tagged/parse.com
- https://serverfault.com/tags/parse
You may also search through existing issues before opening a new one: https://github.com/parse-community/parse-server/issues?utf8=%E2%9C%93&q=is%3Aissue
--- Please use this template. If you don't use this template, your issue may be closed without comment. ---
### Issue Description
Describe your issue in as much detail as possible.
### Steps to reproduce
Please include a detailed list of steps that reproduce the issue. Include curl commands when applicable.
#### Expected Results
What you expected to happen.
#### Actual Outcome
What is happening instead.
### Environment Setup
- **Server**
- parse-server version (Be specific! Don't say 'latest'.) : [FILL THIS OUT]
- Operating System: [FILL THIS OUT]
- Hardware: [FILL THIS OUT]
- Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): [FILL THIS OUT]
- **Database**
- MongoDB version: [FILL THIS OUT]
- Storage engine: [FILL THIS OUT]
- Hardware: [FILL THIS OUT]
- Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): [FILL THIS OUT]
### Logs/Trace
Include all relevant logs. You can turn on additional logging by configuring VERBOSE=1 in your environment.