mirror of
https://github.com/frappe/erpnext.git
synced 2026-05-01 20:48:27 +00:00
43e5dfc3ca
* Revise feature request template for clarity and structure - Updated `about` field to mention "enhancement" - Fixed typo: "many many requests" → "many requests" - Fixed typo: "urgent need to" → "urgent need of" - Added "Before Submitting" checklist to reduce duplicate issues - Improved problem statement placeholder with a role-based example - Added Environment section for ERPNext and Frappe version info * chore: fix case --------- Co-authored-by: Mihir Kandoi <kandoimihir@gmail.com>
2.4 KiB
2.4 KiB
name, about, title, labels, assignees
| name | about | title | labels | assignees |
|---|---|---|---|---|
| Feature request | Suggest an idea or enhancement for ERPNext | feature-request |
Before Submitting
- I searched existing issues and confirmed this is not a duplicate
- This is a feature request, not a bug or support question
- For support: https://discuss.frappe.io/c/erpnext/6
Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. As a [role], I have to [painful task] because [missing feature].
Describe the solution you'd like A clear and concise description of what you want to happen.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Impact
- Blocks critical workflow — no viable workaround
- Significant friction — workaround exists but is painful
- Nice to have — minor improvement
Additional context Add any other context or screenshots about the feature request here.
Environment
- ERPNext Version:
- Frappe Version:
- Deployment: