ERPNext, an open-source ERP software, continues to evolve with active contributions addressing critical bugs and feature enhancements, though financial reporting inaccuracies pose significant challenges.
ERPNext is designed to streamline business management across various domains such as accounting, CRM, and manufacturing. Built on the Frappe Framework, it leverages Python and JavaScript for its operations.
Recent activities highlight a focus on resolving issues related to financial calculations and transaction complexities. The development team is actively engaged in fixing bugs and enhancing features, with notable collaboration among members like Ruthra Kumar and Khushi Rawat. However, unresolved issues in financial modules suggest ongoing risks for users relying on accurate reporting.
Recent issues and pull requests (PRs) indicate a concerted effort to address critical bugs and enhance user experience. Notable issues include discrepancies in financial reports (#42991) and stock valuation errors (#42992). These are complemented by PRs focusing on bug fixes in financial reporting (#42989) and user experience improvements (#42974).
David Arnold (blaggacao)
Ruthra Kumar (ruthra-kumar)
Khushi Rawat (khushi8112)
Nihantra Patel (Nihantra-Patel)
Raffael Meyer (barredterra)
Venkatesh (venkat102)
Rohit Waghchaure (rohitwaghchaure)
Timespan | Opened | Closed | Comments | Labeled | Milestones |
---|---|---|---|---|---|
7 Days | 23 | 8 | 36 | 0 | 1 |
30 Days | 98 | 45 | 147 | 1 | 1 |
90 Days | 294 | 172 | 395 | 1 | 1 |
All Time | 15436 | 13618 | - | - | - |
Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.
Developer | Avatar | Branches | PRs | Commits | Files | Changes |
---|---|---|---|---|---|---|
Frappe PR Bot | 5 | 11/9/0 | 55 | 10 | 474883 | |
Nabin Hait | 4 | 3/3/0 | 7 | 114 | 3854 | |
ruthra kumar | 11 | 11/11/0 | 94 | 28 | 1416 | |
Raffael Meyer | 5 | 9/8/0 | 22 | 41 | 1175 | |
None (mergify[bot]) | 9 | 95/87/4 | 26 | 33 | 1087 | |
rohitwaghchaure | 3 | 17/17/0 | 27 | 42 | 958 | |
Khushi Rawat | 6 | 7/6/0 | 27 | 15 | 836 | |
Lakshit Jain | 7 | 6/2/1 | 12 | 6 | 202 | |
Nihantra C. Patel | 2 | 3/2/0 | 5 | 5 | 135 | |
Dietmar Fischer | 1 | 0/0/0 | 2 | 1 | 31 | |
Shariq Ansari | 2 | 1/0/0 | 4 | 2 | 24 | |
Venkatesh | 3 | 2/2/0 | 5 | 3 | 20 | |
Nicolas Pereira (hqnicolas) | 1 | 2/1/1 | 1 | 4 | 10 | |
Smit Vora | 2 | 3/0/0 | 2 | 1 | 8 | |
Frappe Bot | 2 | 0/0/0 | 3 | 1 | 6 | |
David Arnold | 1 | 1/1/0 | 1 | 2 | 5 | |
Michelle Alva | 1 | 0/0/0 | 1 | 1 | 2 | |
Parameshwari Palanisamy | 2 | 1/1/0 | 2 | 1 | 2 | |
HENRY Florian (FHenry) | 0 | 4/0/1 | 0 | 0 | 0 | |
Rushabh Mehta | 0 | 0/0/0 | 0 | 0 | 0 | |
Kevin Shenk (batonac) | 0 | 1/0/0 | 0 | 0 | 0 | |
None (bhickta) | 0 | 1/0/0 | 0 | 0 | 0 | |
None (lbrandh) | 0 | 1/0/0 | 0 | 0 | 0 | |
Martin Heini (maheini) | 0 | 1/0/0 | 0 | 0 | 0 | |
Carlos (Carlos9k) | 0 | 1/0/1 | 0 | 0 | 0 | |
Phanupong Janthapoon (kurogeek) | 0 | 1/1/0 | 0 | 0 | 0 | |
None (mahowell) | 0 | 1/0/0 | 0 | 0 | 0 | |
Ninad Parikh (Ninad1306) | 0 | 1/0/0 | 0 | 0 | 0 | |
None (Sanket322) | 0 | 1/0/0 | 0 | 0 | 0 | |
None (Zalmelahi) | 0 | 1/0/1 | 0 | 0 | 0 | |
Sagar Vora (sagarvora) | 0 | 1/0/0 | 0 | 0 | 0 | |
Vishnu VS (Vishnu7025) | 0 | 2/0/0 | 0 | 0 | 0 | |
None (jabir-elat) | 0 | 2/0/2 | 0 | 0 | 0 | |
NIYAZ RAZAK (niyazrazak) | 0 | 1/0/0 | 0 | 0 | 0 | |
Diógenes Souza (devdiogenes) | 0 | 1/0/0 | 0 | 0 | 0 | |
Türker Tunalı (TurkerTunali) | 0 | 4/0/2 | 0 | 0 | 0 | |
Kerolles Fathy (KerollesFathy) | 0 | 1/0/0 | 0 | 0 | 0 | |
None (rahulgupta8848) | 0 | 1/0/0 | 0 | 0 | 0 | |
Faris Mohamed (faris-mohamed10) | 0 | 1/0/0 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
The ERPNext project has seen significant recent activity, with 1,818 open issues currently logged. Notably, there are several critical bugs and feature requests that indicate ongoing challenges in areas such as accounting, stock management, and user permissions. The presence of multiple unresolved issues related to financial calculations and document submissions suggests potential risks for users relying on the system for accurate financial reporting and operational efficiency.
A recurring theme among the issues is the complexity of handling transactions across various modules, particularly in relation to pricing rules, tax calculations, and inventory management. This complexity may lead to user frustration and operational inefficiencies.
Issue #42992: Wrong Stock value after sale return
Issue #42991: Accounts Payable Summary Report not matching the General Ledger for Party Type Employee
Issue #42987: Commission Rules like Pricing Rule
Issue #42973: Stock Valuation Method on a Per-Company Basis
Issue #42972: Add Currency from Report Trial Balance for Party
Issue #42961: Error Log re819fr3fq: 'Title' will get truncated, as max characters allowed is 140
Issue #42935: Duplicate items and outdated item price in the Point-of-Sale (POS) item list
Issue #42934: make_payment_request does not set ignore_permissions=True by default anymore
Issue #42932: in BOM Creator the BOM of the sub assembly is not fetched automatically.
Issue #42900: Incorrect Payment Entry grand total outstanding calculation for Journal Entry references.
The analysis of recent issues highlights critical areas needing attention within ERPNext, particularly concerning financial reporting accuracy and user experience during transaction processing. The high volume of unresolved bugs indicates potential risks for users relying on these functionalities for daily operations. The need for enhancements in handling complex pricing rules and multi-currency transactions is evident, suggesting that further development focus is required to address these challenges effectively.
The analysis of the pull requests (PRs) for the ERPNext project reveals a total of 84 open PRs, showcasing a diverse range of fixes, features, and enhancements aimed at improving the functionality and usability of the software. The recent activity indicates a continuous effort by contributors to address bugs, enhance user experience, and implement new features.
PR #42993: fix: added app permission check for apps page
Created 0 days ago. Introduces a permission check for accessing the apps page, enhancing security by ensuring only authorized users can access certain functionalities.
PR #42989: fix: Wrong allocated_amount for sales_team in gross_profit report
Created 1 day ago. Corrects the calculation of allocated amounts in the gross profit report, addressing a significant reporting error that could mislead financial assessments.
PR #42988: fix: adjust price insertion logic for internal suppliers/customers
Created 1 day ago. Fixes an issue with price fetching logic for internal transactions, ensuring accurate pricing is applied.
PR #42978: fix: duplicate items and outdated item price in POS
Created 1 day ago. Resolves issues with outdated pricing displayed on the POS screen, improving accuracy in customer transactions.
PR #42974: fix: retain date filter when redirecting in Profit and Loss report
Created 2 days ago. Enhances user experience by maintaining filter settings during report navigation.
PR #42969: fix: A project without tasks should be able to complete
Created 2 days ago. Fixes a bug preventing projects without tasks from being marked as complete.
PR #42965: fix: resolve gl entries duplication in asset purchase workflow (backport #41845)
Created 2 days ago. Addresses duplication issues in general ledger entries during asset purchases.
PR #42962: refactor: plaid connection
Created 2 days ago. Improves performance and error handling in the Plaid bank connector.
PR #42956: fix(Item): error message on tax rate (backport #42955)
Created 3 days ago. Enhances error messaging related to tax rates for better user clarity.
PR #42953: fix: sync translations from crowdin
Created 3 days ago. Updates translations for various languages, maintaining localization efforts.
PR #42928: fix: getting scrap items from sub assemblies by fetching scrap items for parent BOM
Created 4 days ago. Fixes issues with scrap item retrieval during stock entry creation from work orders.
PR #42926: fix: link Purchase Invoice and Receipt Items to Asset
Created 4 days ago. Introduces fields linking purchase invoice items to assets for better tracking.
PR #42925: fix: Replace add_if_empty
with reset_value
flag
Created 4 days ago. Updates tax handling logic to improve data integrity during document processing.
PR #42902: Update default sales tax for Switzerland
Created 5 days ago. Adjusts sales tax rates in compliance with new regulations in Switzerland.
PR #42901: fix: Serial and Batch Bundle Buying Flow
Created 5 days ago. Addresses issues with serial number management during internal transfers.
16-84. Additional PRs cover various fixes, enhancements, and feature additions across different modules within ERPNext, demonstrating active engagement from contributors to improve the system's functionality and user experience.
The recent pull requests reflect a robust engagement from contributors focused on enhancing ERPNext's functionality through bug fixes, feature improvements, and usability enhancements across various modules such as accounting, inventory management, and project management.
The current state of pull requests in ERPNext demonstrates a vibrant community actively working towards enhancing the software's capabilities while addressing critical issues that affect user experience and data integrity. However, attention should be given to managing open PRs efficiently to ensure timely updates and maintain contributor engagement over time.
David Arnold (blaggacao)
Ruthra Kumar (ruthra-kumar)
Khushi Rawat (khushi8112)
Nihantra Patel (Nihantra-Patel)
Raffael Meyer (barredterra)
Venkatesh (venkat102)
Rohit Waghchaure (rohitwaghchaure)
Others: Several other contributors have been involved in translation fixes, performance improvements, and minor bug fixes.
Active Collaboration: There is significant collaboration among team members, particularly between Ruthra Kumar and Khushi Rawat, indicating a strong teamwork dynamic in addressing complex issues.
Focus on Bug Fixes and Refactoring: The majority of recent commits involve fixing bugs, improving existing features, and refactoring code for better maintainability. This suggests a commitment to enhancing software quality.
Feature Enhancements: New features such as improved UX for tools like Bank Clearance and additional filters in reports indicate ongoing development aimed at user experience improvement.
Translation Updates: Regular updates to translations reflect an effort to support a diverse user base, enhancing accessibility for non-English speakers.
High Volume of Commits: The number of commits from key contributors indicates an active development cycle, with a focus on both new features and resolving existing issues.
Overall, the ERPNext development team demonstrates a robust approach to maintaining and enhancing the software through active collaboration, consistent bug resolution, and feature development.