mirror of
https://github.com/frappe/erpnext.git
synced 2026-05-15 03:01:22 +00:00
24 lines
1.7 KiB
Markdown
24 lines
1.7 KiB
Markdown
## Reporting issues
|
|
|
|
We only accept issues that are bug reports or feature requests. Bugs must be isolated and reproducible problems. Please read the following guidelines before opening any issue.
|
|
|
|
1. **Search for existing issues:** We want to avoid duplication, and you'd help us out a lot by first checking if someone else has reported the same issue. The issue may have already been resolved with a fix available.
|
|
1. **Report each issue separately:** Don't club multiple, unreleated issues in one note.
|
|
1. **Mention the version number:** Please mention the application, browser and platform version numbers.
|
|
|
|
### Issues
|
|
|
|
1. **Share as much information as possible:** Include operating system and version, browser and version, when did you last update ERPNext, how is it customized, etc. where appropriate. Also include steps to reproduce the bug.
|
|
1. **Include Screenshots if possible:** Consider adding screenshots annotated with what goes wrong.
|
|
1. **Find and post the trace for bugs:** If you are reporting an issue from the browser, Open the Javascript Console and paste us any error messages you see.
|
|
1. **Security Issues:** If you are reporting a security issue, please send a private email to <info@frappe.io>.
|
|
|
|
### Feature Requests
|
|
|
|
1. We need as much information you can to consider a feature request.
|
|
1. Think about **how** you want us to build the feature. Consider including:
|
|
1. Mockups (wireframes of features)
|
|
1. Screenshots (annotated with what should change)
|
|
1. Screenshots from other products if you want us to implement features present in other products.
|
|
1. Basically, the more you help us, the faster your request is likely to be completed.
|
|
1. A one line feature request like **Implement Capacity Planning** will be closed. |