Umami, a privacy-focused alternative to Google Analytics, has experienced increased user engagement, reflected in a surge of 68 open issues primarily concerning event tracking and data accuracy. This indicates critical areas needing attention to maintain user trust and satisfaction.
Recent issues and pull requests (PRs) highlight recurring problems with event data logging and display, suggesting potential flaws in the event tracking system. Database migration errors and API response issues further indicate stability concerns.
Mike Cao
Francis Cao
Dependabot[bot]
Minseo Lee
| Timespan | Opened | Closed | Comments | Labeled | Milestones |
|---|---|---|---|---|---|
| 7 Days | 9 | 6 | 7 | 7 | 1 |
| 30 Days | 38 | 19 | 46 | 28 | 1 |
| 90 Days | 83 | 65 | 167 | 56 | 1 |
| 1 Year | 265 | 200 | 801 | 135 | 1 |
| All Time | 1538 | 1470 | - | - | - |
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 |
|---|---|---|---|---|---|---|
| Francis Cao |  |
3 | 0/0/0 | 15 | 19 | 27079 |
| Mike Cao |  |
3 | 1/1/0 | 8 | 8 | 375 |
| Minseo Lee |  |
1 | 5/2/0 | 4 | 3 | 150 |
| dependabot[bot] |  |
1 | 1/1/0 | 1 | 2 | 148 |
| yArna (yArna) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Thomas Vuchot (Tomaas) | 0 | 1/0/1 | 0 | 0 | 0 | |
| Егор (xuserz) | 0 | 1/0/0 | 0 | 0 | 0 | |
| eagleon (eagleon) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Josh Hill (jjjhill) | 0 | 1/0/0 | 0 | 0 | 0 | |
| None (Quadrubo) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Gerard Nesta (gerardnll) | 0 | 0/1/0 | 0 | 0 | 0 | |
| DDDDD12138 (DDDDD12138) | 0 | 1/0/0 | 0 | 0 | 0 | |
| None (sonicbaume) | 0 | 1/0/1 | 0 | 0 | 0 | |
| Robert Silén (robertsilen) | 0 | 1/0/0 | 0 | 0 | 0 | |
| None (dineshsalunke) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Peter Kuhmann (peter-kuhmann) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Kaiwalya Koparkar (kaiwalyakoparkar) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Konstantin Tutsch (konstantintutsch) | 0 | 1/1/0 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
The Umami software project has recently seen a surge in activity with 68 open issues, reflecting ongoing user engagement and a variety of concerns ranging from bugs to feature requests. Notably, issues related to event tracking, data accuracy, and user interface glitches dominate the discussions, indicating areas that may require immediate attention.
Several issues exhibit patterns of recurring problems, particularly around event data not displaying correctly or being logged. This suggests potential underlying flaws in the event tracking system or its integration with the user interface. Additionally, there are multiple reports of errors related to database migrations and API responses, which could indicate broader stability issues within the application.
Issue #2980: The events count in a session detail page is not right
Issue #2979: Data redaction before sending to server
Issue #2977: Custom events filtering
Issue #2975: Adding Elestio as deployment option
Issue #2972: Pretty Up Event Data
Issue #2963: Better Ecommerce tracking
Issue #2962: Loading chunk error after navigating to project event dashboard
Issue #2958: CORS headers not set when deploying to Fly.io
Issue #2954: Feature Request for Hash-Based Routing Analytics
Issue #2949: Using data-umami-event causes a full page reload when clicking the same route repeatedly
The recent activity indicates that users are actively engaging with Umami's features but are encountering significant issues that could hinder their experience and trust in the platform. The prevalence of bug reports related to event tracking and data accuracy suggests that these functionalities may be critical to users' needs and should be prioritized for fixes.
Moreover, the presence of enhancement requests indicates a desire for more robust features, such as better filtering options and improved analytics capabilities, which could enhance user satisfaction if implemented effectively.
The issues surrounding CORS headers and deployment options also highlight potential challenges in integrating Umami into various environments, which could limit its adoption among users with specific hosting requirements.
Overall, addressing these issues promptly could improve user retention and attract new users seeking reliable analytics solutions.
The analysis of the pull requests (PRs) for the Umami project reveals a vibrant and active development environment. The project has seen a mix of feature additions, bug fixes, translation updates, and dependency management efforts. The PRs are well-distributed across various aspects of the project, indicating a comprehensive approach to development and maintenance.
The PRs indicate several key themes in Umami's development:
Feature Enhancements: Many open PRs focus on adding new features or improving existing ones. For instance, PRs like #2976 (one-click deploy options) and #2973 (IP address tracking) show a clear direction towards enhancing user experience and expanding functionality.
Bug Fixes and Improvements: A significant number of PRs address bug fixes or improvements. PR #2974 resolves an inconsistency in event IDs between different databases, which is crucial for maintaining data integrity. Similarly, PR #2971 fixes compatibility issues with data URLs, broadening the application's usability.
Internationalization Efforts: PRs like #2924 highlight ongoing efforts to improve internationalization support. This is vital for Umami's global reach and usability across different languages and regions.
Dependency Management: Regular updates to dependencies (e.g., PR #2968 for Next.js) indicate good maintenance practices, ensuring that Umami remains secure and up-to-date with the latest technology stack.
Community Contributions: The presence of contributions from various developers (e.g., PRs by Kaiwalya Koparkar, Dinesh Salunke, etc.) reflects an active community engagement. This is essential for open-source projects as it brings diverse perspectives and expertise into the development process.
Translation Updates: Several closed PRs focus on updating translations (#2910 for Korean translations, #2904 for German translations). This attention to localization is crucial for enhancing user experience in non-English speaking regions.
In conclusion, Umami's pull request activity demonstrates a healthy balance of feature development, bug fixing, community involvement, and maintenance efforts. This proactive approach not only enhances the software's capabilities but also ensures its reliability and usability across different environments and languages.
Mike Cao (mikecao)
Francis Cao (franciscao633)
Dependabot[bot]
Minseo Lee (quiple)
The development team is effectively managing ongoing updates and improvements within the Umami project. The collaborative nature of the commits suggests a well-coordinated effort to enhance functionality while maintaining code quality through regular merges and dependency updates.
Summary
Quantified Reports
Detailed Reports