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
ian		3	1/0/0	11	98	4790
dependabot[bot]		1	51/39/12	39	34	3161
Florian Strasser		1	0/1/0	1	8	2549
Rijk van Zanten		3	6/6/0	28	123	1220
Kevin Lewis		2	4/4/0	7	6	858
Hannes Küttner		3	4/4/0	15	31	511
Nitwel (Nitwel)		1	1/0/0	6	16	293
Pascal Jufer		2	8/8/0	9	20	232
Alex Gaillard		1	0/1/0	2	6	230
Dominic Marcelino		1	4/4/0	4	7	221
daedalus		3	9/8/0	14	20	212
Brainslug		2	2/1/0	5	14	208
Connor Winston		2	1/1/0	3	4	199
José Varela		3	3/4/0	6	18	193
AndriyStankevych		1	1/1/0	1	4	174
renovate[bot]		1	3/3/0	3	6	151
Jan Arends		1	2/1/1	1	7	92
SP12893678		1	6/3/1	3	10	86
Anton Fedorov		1	1/1/0	1	5	74
Florian C. Wachmann		1	3/2/0	3	7	56
Shane		1	1/1/0	1	5	50
keesvanbemmel		1	1/1/0	1	4	41
Gerard Lamusse		1	3/2/0	2	3	23
Bernat Vadell		1	0/0/0	1	3	13
HeikoMueller		1	1/1/0	1	3	12
Hugo Torzuoli		1	2/1/1	1	3	9
Joshua Bemenderfer		1	1/1/0	1	2	8
Sim Boon Long		1	1/1/0	1	3	8
Jan Piotrowski		1	1/1/0	1	2	7
Fatuma Abdullahi		1	1/1/0	1	2	7
Lfillon		1	1/1/0	1	3	7
max		1	1/1/0	1	2	6
Manuel		1	1/1/0	1	2	3
Maxime Britto		1	1/1/0	1	2	3
Niklas Bittner (Trup3s)		0	1/0/0	0	0	0
MIAUYO (miauyo)		0	2/0/2	0	0	0
Matthew Rollinson (matt-rolley)		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 Directus project has recently seen a surge in activity, with 492 open issues currently logged. Notably, several issues have been created or updated within the last few days, indicating an active engagement from both users and developers. A recurring theme is the presence of bugs related to permissions, user interface inconsistencies, and functionality enhancements.

Several issues highlight critical bugs that could impact user experience, such as problems with the WYSIWYG editor, permissions not being enforced correctly, and unexpected behaviors in relation to many-to-many (M2M) relationships. The presence of multiple issues regarding user permissions suggests a potential area for improvement in the system's access control mechanisms.

Issue Details

Recent Issues

1. Issue #23692: Collections created under a group not being removed during schema sync

   • Priority: High
   • Status: Open
   • Created: 0 days ago
   • Updated: N/A

2. Issue #23688: Add duplicate function to Assets Service

   • Priority: Medium
   • Status: Open
   • Created: 1 day ago
   • Updated: N/A

3. Issue #23687: Error when switching between two kanban layout Bookmarks in different Collections

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

4. Issue #23686: Allow opening relational item in drawer when readonly

   • Priority: Medium
   • Status: Open
   • Created: 1 day ago
   • Updated: N/A

5. Issue #23684: Conditions that add new choices will overwrite choices with same index

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

6. Issue #23683: Conditional to change WYSIWYG Toolbar is not working

   • Priority: Medium
   • Status: Open
   • Created: 2 days ago
   • Updated: N/A

7. Issue #23670: Table view for content types doesn't display records

   • Priority: High
   • Status: Needs Info
   • Created: 3 days ago
   • Updated: 2 days ago

8. Issue #23669: Getting "Error: XMLHttpRequest is not defined" when doing requests in Node

   • Priority: High
   • Status: Open
   • Created: 4 days ago
   • Updated: N/A

9. Issue #23667: After changing sort of primary field, Primary key must be unique error occurs.

   • Priority: Medium
   • Status: Open
   • Created: 4 days ago
   • Updated: N/A

10. Issue #23662: The accountability property when instantiating a service does not default to admin.

    • Priority: Medium
    • Status: Needs Info
    • Created: 5 days ago
    • Updated: N/A

Themes and Commonalities

• Many recent issues revolve around permission handling and user access controls, indicating potential weaknesses in the current implementation.
• Bugs related to UI components like the WYSIWYG editor and table views suggest that user experience is a significant concern.
• There are also enhancement requests for features that would improve usability, such as adding functions to existing services or improving error handling.
• The presence of multiple issues related to M2M relationships indicates complexity and possible confusion among users when managing these relationships.

Overall, while there is active engagement from the community and developers, addressing these critical issues will be essential for maintaining user satisfaction and system integrity moving forward.

Report On: Fetch pull requests

Overview

The analysis of the Directus project's pull requests (PRs) reveals a dynamic and active development environment with a focus on enhancing functionality, fixing bugs, and improving user experience. The project has a significant number of open PRs, indicating ongoing work and community involvement in its development.

Summary of Pull Requests

Open Pull Requests

1. PR #23691: Addresses websocket authentication handling issues. It refactors authentication logic to ensure proper error handling and connection closure.
2. PR #23685: Fixes an issue with overwriting choices in conditions within the application, ensuring that conditions do not unintentionally overwrite existing choices.
3. PR #23639: Implements cache busting for image previews generated from Cloudinary, allowing for the latest images to be displayed without caching issues.
4. PR #23612: Reduces dependencies on activity and revisions tables by extracting comments to a separate table and consolidating content versioning.
5. PR #23579: Ensures that database string types are preserved during schema imports, preventing unintended type changes.
6. PR #23563: Updates translations through Crowdin, enhancing localization support across various languages.
7. PR #23550: Improves calendar layout by adjusting event displays based on date types, enhancing visual consistency and usability.
8. PR #23410: Adds retention support for directus_activity and directus_revisions, allowing for better data management and compliance with data retention policies.

Closed Pull Requests

1. PR #23690: Updates the tj-actions/changed-files GitHub action to version 45, improving the workflow for detecting changed files in PRs.
2. PR #23689: Updates the docker/build-push-action to version 6, ensuring compatibility with the latest Docker build and push capabilities.
3. PR #23682: Updates happy-dom to version 15, enhancing testing capabilities with improved DOM emulation.
4. PR #23681: Updates rollup-plugin-node-externals to version 6, optimizing Rollup builds by excluding node_modules from the bundle.
5. PR #23679: Updates @sinclair/typebox to version 0.33.11, incorporating the latest type definitions and features.

Analysis of Pull Requests

The Directus project demonstrates a robust approach to continuous improvement through its pull request activities. The open PRs reflect a commitment to enhancing security (e.g., PR #23691), fixing bugs (e.g., PR #23685), and improving user experience (e.g., PR #23550). The presence of PRs addressing localization (e.g., PR #23563) indicates an effort to cater to a global audience.

Closed PRs show active maintenance of dependencies and tools used within the project (e.g., updates to GitHub actions and testing libraries). This not only ensures compatibility with the latest technologies but also enhances the development workflow efficiency.

The diversity in PR topics—from security fixes and bug resolutions to feature enhancements—highlights the project's comprehensive development strategy aimed at delivering a reliable and user-friendly product.

In conclusion, Directus's pull request management reflects an organized effort towards maintaining high standards of software quality, security, and user satisfaction through active community involvement and continuous integration practices.

Report On: Fetch commits

Repo Commits Analysis

Development Team and Recent Activity

Team Members and Activities

1. renovate[bot]

   • Commits: 3
   • Changes: 151 across 6 files.
   • Focus: Dependency updates.

2. paescuj (Pascal Jufer)

   • Commits: 9
   • Changes: 232 across 20 files.
   • Collaborations: Worked with Rijk van Zanten and others.
   • Focus: Various enhancements and dependency updates.

3. dependabot[bot]

   • Commits: 39
   • Changes: 3161 across 34 files.
   • Focus: Dependency updates, significant activity in managing package versions.

4. rijkvanzanten (Rijk van Zanten)

   • Commits: 28
   • Changes: 1220 across 123 files.
   • Collaborations: Frequently worked with Hannes Küttner and Pascal Jufer.
   • Focus: Major feature implementations, bug fixes, and documentation updates.

5. connorwinston (Connor Winston)

   • Commits: 3
   • Changes: 199 across 4 files.
   • Focus: Fixing the Color Select Interface.

6. ComfortablyCoding (daedalus)

   • Commits: 14
   • Changes: 212 across 20 files.
   • Collaborations: Worked with various team members on multiple features and fixes.

7. SP12893678

   • Commits: 3
   • Changes: 86 across 10 files.
   • Focus: Bug fixes and minor enhancements.

8. u12206050 (José Varela)

   • Commits: 6
   • Changes: 193 across 18 files.
   • Collaborations: Worked closely with Rijk van Zanten on several features.

9. br41nslug (Brainslug)

   • Commits: 5
   • Changes: 208 across 14 files.
   • Focus: WebSocket controller improvements.

10. phazonoverload (Kevin Lewis)

    • Commits: 7
    • Changes: 858 across 6 files.
    • Focus: Documentation updates and feature enhancements.

11. formfcw (Florian C. Wachmann)

    • Commits: 3
    • Changes: 56 across 7 files.
    • Focus: UI improvements and bug fixes.

12. Additional contributors include:

    • GuyShane, Dominic-Marcelino, McSundae, JoshTheDerf, HZooly, FatumaA, maxsteinwand, etc., each contributing varying degrees of commits focused on bug fixes, documentation, and feature enhancements.

Patterns and Themes

• The development team exhibits a strong focus on dependency management through automated tools like Renovate Bot and Dependabot, indicating a proactive approach to keeping the project up-to-date with the latest libraries.
• Collaborations are frequent among team members, particularly between Rijk van Zanten, Pascal Jufer, and Hannes Küttner, suggesting a cohesive team dynamic that enhances productivity.
• There is a consistent effort towards improving user interfaces and fixing bugs related to existing functionalities, as seen in the recent commits by Connor Winston and Florian C. Wachmann.
• The presence of numerous changesets indicates ongoing enhancements to the platform's capabilities alongside regular maintenance tasks such as documentation updates and refactoring efforts.
• The project shows a healthy mix of feature development alongside critical bug fixes, reflecting an agile response to user needs and technical debt management.

Conclusions

The Directus development team is actively engaged in enhancing the platform through collaborative efforts focused on both new features and maintenance tasks. The use of automated tools for dependency management reflects a commitment to code quality and stability while fostering an environment conducive to teamwork and shared ownership of the codebase.