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
Yuval Hazaz		4	23/14/1	51	250	10672
Mor Hagbi		2	5/4/1	26	38	6223
None (dependabot[bot])		5	17/0/16	5	3	4933
Muly Gottlieb		1	6/6/0	10	32	266
amplication-engineering		1	0/0/0	4	3	12
Pavan Emani (p1kalys)		0	0/1/0	0	0	0
None (haimbell)		0	0/1/0	0	0	0
None (Pharma-22)		0	2/0/2	0	0	0
None (amplication[bot])		0	5/0/5	0	0	0

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

Report On: Fetch issues

Recent Activity Analysis

The Amplication project currently has 550 open issues, indicating a high level of ongoing development and user engagement. Notably, several recent issues highlight critical bugs related to the user experience and functionality of the platform, particularly concerning the setup and integration processes. A recurring theme is the need for improved documentation and clarity in error messages, which suggests that users may be facing challenges navigating the platform effectively.

Several urgent issues remain unaddressed, including significant bugs that impact the ability to create and manage services effectively. This could lead to frustration among users and potentially hinder adoption if not resolved promptly.

Issue Details

Recent Issues

1. Issue #8965: Template creation wizard: Add No-DB option

   • Priority: Normal
   • Status: Open
   • Created: 0 days ago
   • Description: Request to add a "No-DB" option in the service template creation wizard.

2. Issue #8963: Template creation wizard- update texts

   • Priority: Normal
   • Status: Open
   • Created: 0 days ago
   • Description: Update various texts in the template creation wizard for clarity.

3. Issue #8956: 🐛 Bug Report: Fresh Start Project Unusable - Documentation Outdated, Missing Critical Services

   • Priority: High
   • Status: Open
   • Created: 2 days ago
   • Description: Users face numerous errors when following outdated documentation for local development, leading to a non-functional setup.

4. Issue #8954: Bug: After deleting a service, an empty page is displayed

   • Priority: Normal
   • Status: Open
   • Created: 2 days ago
   • Description: Deleting a service results in an empty page instead of redirecting or displaying a confirmation message.

5. Issue #8951: Service Template: Improve experience

   • Priority: Normal
   • Status: Open
   • Created: 2 days ago
   • Description: Suggestions for enhancing the user experience in managing service templates.

6. Issue #8950: Bug Report: Cannot send an invite for a user that was removed from the workspace

   • Priority: High
   • Status: Open
   • Created: 3 days ago
   • Description: Users cannot re-invite previously removed users due to existing invitation conflicts.

7. Issue #8942: Service Catalog: Additional Columns

   • Priority: Normal
   • Status: Open
   • Created: 4 days ago
   • Description: Proposal to add more columns to the Service Catalog view for better information display.

8. Issue #8941: Service Catalog: The "Last Build" and "Code Gen Version" columns should reflect the last successful build

   • Priority: Normal
   • Status: Open
   • Created: 4 days ago
   • Description: Request to update column titles and content for clarity on build statuses.

9. Issue #8940: Service Catalog: Display the Services and Templates catalogs

   • Priority: Normal
   • Status: Open
   • Created: 4 days ago
   • Description: Suggestion to improve the catalog tab layout for better usability.

10. Issue #8939: Service Catalog: Update names

    • Priority: Normal
    • Status: Open
    • Created: 4 days ago
    • Description: Request to rename the Overview tab to "Catalog" for consistency.

Implications

The presence of critical bugs such as those reported in issues #8956 and #8954 indicates potential barriers to effective use of Amplication, particularly for new users attempting to set up projects. The need for clearer documentation is echoed across multiple issues, suggesting that improving user guidance could significantly enhance user experience and reduce frustration.

Moreover, ongoing feature requests like those in issues #8965 and #8963 show that while users are engaged with the platform's capabilities, they are also seeking enhancements that could streamline workflows further. Addressing these concerns promptly will be crucial in maintaining user satisfaction and fostering continued growth within the community.

Summary of Issues

• Total Open Issues: 550
• Recent Notable Issues:
• #8965 (New Feature)
• #8963 (Text Updates)
• #8956 (Critical Bug)
• #8954 (Bug)
• #8951 (User Experience Improvement)

This analysis highlights both challenges and opportunities for improvement within the Amplication project as it continues to evolve.

Report On: Fetch pull requests

Overview

The provided datasets include a comprehensive list of pull requests (PRs) from the Amplication project repository. The PRs cover various aspects of the project, including feature additions, bug fixes, dependency updates, and refactoring efforts. The analysis will focus on the themes and trends observed in these PRs, highlighting significant contributions and changes made to the project.

Summary of Pull Requests

Open Pull Requests

1. PR #8964: Introduces dynamic text for wizard steps in the client application. It includes several commits that add new constants and update existing components to use dynamic text.
2. PR #8962: Updates dependencies find-my-way and fastify to their latest versions, addressing security vulnerabilities and improving functionality.
3. PR #8961: Implements hooks to use base URLs for resources and projects, enhancing the configuration flexibility of the client application.
4. PR #8960: Similar to PR #8961, it focuses on using base URLs but is part of a different branch, indicating ongoing work in this area.
5. PR #8959: Removes an unused module for resource packages, streamlining the codebase.
6. PR #8958: Continues work on using base URLs, suggesting iterative development on this feature.
7. PR #8957: Another iteration on using base URLs, showing a concentrated effort to enhance this aspect of the application.
8. PR #8955: Fixes an issue with event propagation on dialog clicks, improving user interaction handling in the client application.

Closed Pull Requests

1. PR #8945: Aligns the Data Service Generator (DSG) package.json with the main monorepo configuration, ensuring consistency across packages.
2. PR #8944: A release PR for version v3.2.3, merging multiple feature additions and fixes into the next branch.
3. PR #8943: Allows workspace creation for new users regardless of entitlement settings, addressing a specific user experience issue.
4. PR #8937: Adds a new entitlement for workspace creation, integrating with the previous PR to enhance permission management.
5. PR #8933: Moves private plugins' settings to a separate tab on the project page, improving UI organization and accessibility.
6. PR #8931: Displays code generation versions in resource lists and adds support for sorting non-string columns, enhancing data visibility and management capabilities.
7. PR #8929: Introduces a new data grid component for resource lists, significantly upgrading UI interactions and data handling.

Analysis of Pull Requests

The analysis of the pull requests reveals several key themes and trends in the development of the Amplication project:

Focus on Enhancements and Features

• A significant number of PRs are dedicated to enhancing existing features or adding new ones. For instance, PRs like #8964 (dynamic text for wizard steps), #8958 (#8957) (base URL usage), and #8929 (data grid for resource lists) indicate ongoing efforts to improve user experience and functionality.

Iterative Development

• Many PRs appear to be iterations on previously introduced features or enhancements. For example, multiple PRs related to using base URLs (#8961, #8960) suggest an iterative approach to refining this functionality based on feedback or further requirements.

Dependency Management

• Regular updates to dependencies (#8962) highlight an active approach towards maintaining security and compatibility within the project ecosystem.

Community Engagement

• The presence of contributions from various developers (e.g., Yuval Hazaz, Muly Gottlieb) suggests a collaborative development environment where community input is valued and integrated into the project's evolution.

Codebase Optimization

• Efforts like removing unused modules (#8959) reflect a commitment to keeping the codebase clean and efficient, which is crucial for long-term maintainability.

Release Management

• The structured approach towards releases (#8944) indicates a well-defined process for integrating new features and fixes into stable versions of the software.

Overall, the pull requests demonstrate a robust development activity within the Amplication project, characterized by continuous improvement efforts, active community involvement, and a strong focus on enhancing both functionality and user experience.

Report On: Fetch commits

Repo Commits Analysis

Development Team and Recent Activity

Team Members

1. Muly Gottlieb (mulygottlieb)

   • Recent Activity:
   • Merged multiple pull requests related to version updates and bug fixes.
   • Worked on enhancements for the data service generator and server components.
   • Collaborated with other team members on various features, including a new entitlement for workspace creation.
   • Notable contributions include aligning package.json files and fixing tests.

2. Mor Hagbi (morhag90)

   • Recent Activity:
   • Focused on updating snapshots and enhancing the data service generator.
   • Contributed significantly to bug fixes in server components, particularly around workspace creation and authentication.
   • Engaged in feature development, including the addition of a new login form component.

3. Yuval Hazaz (yuval-hazaz)

   • Recent Activity:
   • High volume of commits, focusing on client-side improvements, including dynamic text usage in wizards and service templates.
   • Worked on removing unused code and enhancing user interface components.
   • Collaborated on platform routes and service templates, contributing to both client and server aspects.

4. Dependabot (dependabot[bot])

   • Recent Activity:
   • Automated dependency updates across multiple branches, ensuring libraries like fastify, find-my-way, and others are up-to-date.
   • Contributed to maintaining the health of the project by addressing security vulnerabilities.

Patterns, Themes, and Conclusions

• High Collaboration: The team exhibits strong collaboration, with multiple merges involving contributions from different members. Muly Gottlieb appears to lead many merges, indicating a central role in managing pull requests.
• Focus on Bug Fixes and Enhancements: Recent activities show a balance between fixing bugs and developing new features, particularly in the data service generator and client-side components.
• Dynamic Feature Development: Yuval Hazaz's contributions highlight an emphasis on improving user experience through dynamic content and UI adjustments.
• Automated Maintenance: Dependabot's activity reflects a proactive approach to dependency management, which is crucial for maintaining project stability.
• Active Development Cycle: The frequency of commits and merges indicates a robust development cycle, with ongoing enhancements that align with user needs and project goals.

Overall, the development team is actively engaged in improving the Amplication platform while ensuring code quality through collaborative efforts and automated tools.