Quantify Issues

Recent GitHub Issues Activity

_{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.}

Quantify commits

Quantified Commit Activity Over 30 Days

Developer	Avatar	Branches	PRs	Commits	Files	Changes
Mike Cao		1	3/3/0	55	564	11514
Francis Cao		1	1/1/0	32	60	1772
Sergey Lisovskiy		1	1/1/0	1	1	364
Minoru Maekawa		1	1/1/0	1	1	84
Gerard Nesta		1	2/1/0	1	1	26
Raye Evtuch		1	1/1/0	1	3	11
wjsoj		1	1/1/0	1	1	9
boforetech		1	1/1/0	1	1	2
Chris Heinz (Cuzart)		0	0/1/0	0	0	0
eagleon (eagleon)		0	0/1/0	0	0	0
None (er-santosh)		0	1/0/1	0	0	0
Bruno Parmentier (bparmentier)		0	1/0/0	0	0	0
Lena Emme (Feuerhamster)		0	0/1/0	0	0	0
LAHLOU Mohamed (LahlouMohamed)		0	0/0/1	0	0	0
Israel Ortiz de Zárate (israelozarate7)		0	0/1/0	0	0	0
Konstantin Tutsch (konstantintutsch)		0	1/0/0	0	0	0

_{PRs: created by that dev and opened/merged/closed-unmerged during the period}

Report On: Fetch issues

Recent Activity Analysis

The Umami project has seen a significant amount of recent activity on GitHub, with 49 open issues currently being tracked. Among these, several issues have been created or updated in the last few days, indicating ongoing user engagement and potential areas of concern that need addressing. Notably, there are recurring themes related to installation problems, event tracking discrepancies, and feature requests for improved analytics capabilities.

Several issues highlight critical bugs or complications, such as the inability to view event data despite successful tracking (#2886), and problems with Docker deployments leading to migration errors (#2645). Additionally, there are discussions around enhancing user experience through better documentation and feature requests for more granular analytics options.

Issue Details

Most Recently Created Issues:

1. Issue #2907: husky - .git can't be found

   • Priority: High
   • Status: Open
   • Created: 1 day ago
   • Update: N/A

2. Issue #2906: Failed to start on v2.13.1 with docker & postgres

   • Priority: High
   • Status: Open
   • Created: 1 day ago
   • Update: N/A

3. Issue #2889: load via js directly instead of script tag

   • Priority: Medium
   • Status: Open
   • Created: 5 days ago
   • Update: Edited 1 day ago

4. Issue #2887: Allow public sharing of real-time dashboard

   • Priority: Medium
   • Status: Open
   • Created: 6 days ago
   • Update: N/A

5. Issue #2881: CORS Policy Issue with Umami Cloud API Access

   • Priority: High
   • Status: Open
   • Created: 12 days ago
   • Update: Edited 0 days ago

Most Recently Updated Issues:

1. Issue #2902: The data shown in the chart is incomplete

   • Priority: Bug
   • Status: Closed (fixed in dev)
   • Updated: 2 days ago

2. Issue #2901: Error 500 when trying to view custom event properties

   • Priority: Bug
   • Status: Closed (fixed in dev)
   • Updated: 2 days ago

3. Issue #2899: event_data table empty and dashboard events page (Postgres) while front-end fires /api/send requests for the events

   • Priority: Bug
   • Status: Closed (resolved)
   • Updated: 2 days ago

4. Issue #2898: Session history not sorted correctly

   • Priority: Bug
   • Status: Closed (fixed in dev)
   • Updated: 1 day ago

5. Issue #2897: Data is not sorted correctly

   • Priority: Bug
   • Status: Closed (fixed in dev)
   • Updated: 1 day ago

Themes and Commonalities

The recent issues reflect several common themes:

• Users are experiencing difficulties with Docker deployments, particularly concerning migrations and environment configurations.
• There are multiple reports of event tracking inconsistencies, where events are logged but not displayed correctly in the dashboard.
• Feature requests indicate a desire for enhanced functionality, such as improved filtering options and better handling of query parameters.
• Documentation improvements are frequently requested to aid users in navigating setup and troubleshooting processes.

These recurring themes suggest that while Umami is actively developed and maintained, there are significant areas requiring attention to improve user experience and system reliability.

Report On: Fetch pull requests

Overview

The analysis of the pull requests (PRs) for the Umami software project reveals a total of 7 open PRs and 859 closed PRs, with a focus on language translations, bug fixes, and feature enhancements. The recent activity indicates ongoing development, particularly in improving localization and addressing technical issues.

Summary of Pull Requests

Open Pull Requests

• PR #2905: Update ca-ES.json
  Created 2 days ago. This PR updates a Catalan translation file with a minor correction. It reflects ongoing efforts to maintain accurate localization.

• PR #2904: Update German translation
  Created 2 days ago, edited 1 day ago. This PR improves the German translations and adds new entries, demonstrating active engagement in localization efforts.

• PR #2890: Use init when running in Docker to avoid zombie process
  Created 3 days ago. This PR addresses a technical issue with Docker processes by implementing an init flag to prevent zombie processes, indicating attention to deployment stability.

• PR #2678: #2665 fix proposal
  Created 132 days ago. This PR aims to restore client-side search functionalities that were previously removed, showing a focus on user experience improvements.

• PR #2638: chore: high quality icons
  Created 145 days ago. This PR proposes enhancements to icon quality, indicating an effort to improve the visual aspects of the application.

• PR #2436: Allow setting custom data on autotracked pageviews via data attribute on script element
  Created 253 days ago. This feature allows users to set custom data for tracking page views, enhancing the flexibility of analytics.

• PR #2040: wip: feat: support mongodb connection
  Created 469 days ago. This is a work-in-progress PR aimed at adding MongoDB support, which could significantly broaden the database options for users.

Closed Pull Requests

• PR #2903: v2.13.1
  Closed 2 days ago after merging several updates including language files and bug fixes, showcasing regular maintenance and versioning practices.

• PR #2900: Update ca-ES.json
  Closed 2 days ago. Similar to PR #2905, this update reflects ongoing localization efforts.

• PR #2895: Updated ja-JP
  Closed 2 days ago. This PR updates Japanese translations, further emphasizing the project's commitment to localization.

• PR #2894: Update ja-JP.json
  Closed 2 days ago. Another update for Japanese translations, indicating consistent attention to language support.

• PR #2892: v2.13.0
  Closed 3 days ago after merging various updates and improvements as part of the versioning process.

Analysis of Pull Requests

The pull requests for the Umami project reflect several key themes and trends that are critical to understanding its development trajectory:

1. Localization Efforts: A significant number of recent PRs focus on updating and improving translations across multiple languages (e.g., German, Japanese, Catalan). This indicates a strong commitment to making Umami accessible to a diverse user base, which is essential for a privacy-focused analytics tool that aims to attract users from various regions.

2. Technical Stability and Bug Fixes: Several open PRs address technical issues such as Docker process management (PR #2890) and type errors (PR #2891). These efforts are vital for maintaining the reliability of the software as it scales and evolves. The presence of closed PRs that fix bugs or enhance features also suggests an active approach to quality assurance.

3. Feature Enhancements: The introduction of features like custom data attributes for page views (PR #2436) and support for MongoDB (PR #2040) demonstrates an ongoing effort to expand Umami's capabilities beyond basic analytics tracking. These enhancements cater to user needs for more customizable analytics solutions.

4. Community Engagement: The discussions around certain PRs indicate active community involvement, with contributors seeking feedback and clarifications on implementation details (e.g., PR #2873 regarding website transfer permissions). This engagement is crucial for fostering a collaborative environment where contributors feel valued and motivated to participate.

5. Old Pull Requests: Some older PRs remain open or have not been merged despite being relevant (e.g., PR #2040). This could indicate potential bottlenecks in the review process or prioritization challenges within the development team. Addressing these older requests may help improve community trust and encourage further contributions.

6. Lack of Recent Merge Activity: While there are many open PRs, some have been pending for extended periods without resolution or feedback (e.g., PR #2678). A backlog of unresolved issues can lead to frustration among contributors and may hinder project momentum if not managed effectively.

In conclusion, the Umami project exhibits robust activity in terms of localization, technical improvements, and feature expansions while also highlighting areas where community engagement and backlog management could be enhanced for better overall project health.

Report On: Fetch commits

Repo Commits Analysis

Development Team and Recent Activity

Team Members and Recent Activities

• Mike Cao (mikecao)

  • Recent Commits: 55 commits with significant changes across various files.
  • Key Contributions:
  • Merged multiple pull requests related to language updates and bug fixes.
  • Worked on fixing UTC issues, updating session properties, and enhancing the user interface for session metrics.
  • Implemented updates for real-time data fetching and session statistics.
  • Collaborated with other team members on language translations and feature enhancements.

• Francis Cao (franciscao633)

  • Recent Commits: 32 commits focusing on bug fixes and feature improvements.
  • Key Contributions:
  • Addressed various bugs related to session data queries, including fixing order by issues and improving query performance.
  • Worked on enhancing the real-time data handling and session metrics display.
  • Collaborated closely with Mike Cao on multiple merges into the dev branch.

• Gerard Nesta (gerardnll)

  • Recent Commits: 1 commit focused on updating language files.
  • Key Contributions:
  • Contributed to the localization efforts by updating the ca-ES.json file.

• Minoru Maekawa (err931)

  • Recent Commits: 1 commit updating language files.
  • Key Contributions:
  • Updated the ja-JP.json file as part of localization efforts.

• Wjsoj

  • Recent Commits: 1 commit fixing a small type error in the codebase.

• Raye Evtuch

  • Recent Commits: 1 commit related to transferring website permissions for team managers.

• Sergey Lisovskiy (lsvs)

  • Recent Commits: 1 commit updating Belarusian translations.

Patterns, Themes, and Conclusions

• Active Development: The team has been actively merging pull requests, indicating a collaborative environment focused on continuous improvement of the Umami project.
• Focus on Localization: There is a strong emphasis on localization with multiple updates to language files, reflecting the project's commitment to accessibility for diverse users.
• Bug Fixes and Enhancements: Recent activities show a pattern of addressing bugs, particularly around session data handling and real-time analytics, which are crucial for maintaining user trust in analytics accuracy.
• Collaboration: Mike Cao appears to be a central figure in the development process, frequently merging contributions from other team members and leading significant updates. This suggests a well-defined leadership role within the team structure.
• Feature Expansion: The ongoing work on session metrics and real-time data indicates a focus on enhancing user experience and functionality, aligning with Umami's goal of being a robust alternative to traditional analytics tools.

Overall, the development team is demonstrating effective collaboration towards enhancing Umami's features while ensuring high standards of quality through regular bug fixes and updates.