GitHub Projects Bug Skews Software Project Statistics for Epic Progress
Accurate software project statistics are crucial for effective project management, resource allocation, and assessing team performance. However, a recent discussion on GitHub’s community forums highlights a significant bug in GitHub Projects that is undermining this very foundation, particularly concerning the progress tracking of Epic sub-issues.
The Problem: Misleading Epic Progress Indicators
The issue, reported by Mikolasch, details a critical discrepancy in how GitHub Projects displays progress for Epic-linked sub-issues. Mikolasch observed that an Epic with four completed sub-issues (e.g., #35, #36, #37, #38 linked to Epic #34) incorrectly showed a progress indicator of '0/1' instead of the expected '4/4' or at least '0/4'. This means that regardless of the actual number of sub-issues or their completion status, the project board consistently displayed '0/1'.
The expected behavior is for the progress indicator to reflect the total count of linked sub-issues and the number completed, providing a clear, at-a-glance overview of an Epic's status. Instead, the '0/1' display renders the progress tracking feature largely ineffective for Epics, making it challenging to get reliable software project statistics.
Steps to Reproduce:
- Navigate to a Project board.
- View an Epic with linked sub-issues in the project view.
- Observe the progress indicator, which incorrectly displays '0/1'.
Attempted Workarounds:
Mikolasch attempted standard troubleshooting steps, including refreshing the page (F5), navigating away and back to the Epic, and reloading the entire Project view. None of these actions resolved the issue, indicating a persistent bug within the platform itself.
Community Reaction and Impact
The community quickly echoed Mikolasch's concerns. User kchoudhu succinctly captured the frustration, stating, "Just about impossible to do real work using this system if it can't do basic stuff like, you know, count issues." This sentiment underscores the severe impact such a bug has on developer productivity and project oversight. When fundamental tracking mechanisms fail, it directly impedes a team's ability to monitor progress, especially for complex initiatives often structured as Epics.
Another user, Waxo, suggested a possible duplicate issue (#193565), indicating that this might not be an isolated incident. Furthermore, svioletg confirmed the bug, noting they "Came here from Google to check if I did something wrong, guess this is a recent bug. Having the same issue here." The fact that users are actively searching for solutions and confirming the problem highlights its widespread nature and the urgent need for a fix.
For teams relying on GitHub Projects for their agile workflows, this bug can significantly disrupt planning and reporting. Accurate progress indicators are vital for tracking software engineer OKR (Objectives and Key Results) and for providing data points that might be used in software engineer performance review examples. Without reliable metrics, managers and team leads struggle to make informed decisions, assess project health, and communicate status effectively to stakeholders.
GitHub's Acknowledgment
While no immediate solution or workaround was provided, the GitHub Actions bot promptly acknowledged the feedback, assuring users that their input would be reviewed by product teams. This acknowledgment is a standard response for bug reports and feature requests, indicating that the issue has entered the official feedback pipeline.
Conclusion
The incorrect progress indicator for Epic sub-issues in GitHub Projects is a significant impediment to effective project management and accurate software project statistics. This bug not only frustrates users but also undermines the reliability of GitHub Projects as a comprehensive project tracking tool. As the community awaits a fix, this discussion serves as a crucial reminder of the importance of robust and accurate tooling in maintaining developer productivity and ensuring project success. We encourage all users experiencing this issue to upvote the original discussion and add their insights to help prioritize a resolution.
