mirror of
https://github.com/frappe/erpnext.git
synced 2026-02-12 17:23:38 +00:00
Updated Issue Guidelines (markdown)
@@ -1,8 +1,10 @@
|
||||
### Introduction (first timers)
|
||||
|
||||
Thank you for your interest in raising an Issue with ERPNext. An Issue could mean a bug report or a request for a missing feature. By raising a bug report, you are contributing to the development of ERPNext and this is the first step of participating in the community. Bug reports are very helpful for developers as they quickly fix the issue before other users start facing it.
|
||||
Thank you for your interest in raising an Issue with ERPNext on [github](https://github.com/frappe/erpnext/issues).
|
||||
|
||||
Feature requests are also a great way to take the product forward. New ideas can come in any user scenario and the issue list also acts a roadmap of future features.
|
||||
An Issue could mean a **bug report** or a **request for a missing feature**. By raising a bug report, you are contributing to the development of ERPNext and this is the first step of participating in the community.
|
||||
- **Bug reports** are very helpful for developers as they point them to which problems need to be fixed before other users start facing it.
|
||||
- **Feature requests** are also a great way to take the product forward. New ideas can come in any user scenario and the issue list also acts a roadmap of future features.
|
||||
|
||||
When you are raising an Issue, you should keep a few things in mind. Remember that the developer does not have access to your machine so you must give all the information you can while raising an Issue. If you are suggesting a feature, you should be very clear about what you want.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user