Unpacking GitHub Projects V2: Why Your Items Might Be Missing from Collections

GitHub Projects V2 is a powerful platform designed to enhance team collaboration and streamline project management. However, even the most robust development productivity tools can encounter unexpected glitches. A recent discussion in the GitHub Community highlights a peculiar bug where project items, though demonstrably present and accessible via direct node IDs, fail to appear in collection queries.

The Case of the Disappearing Project Items

User soonthorn707 brought attention to a critical discrepancy within their GitHub Projects V2 setup. In their project, "Project 6 — Roadmap" (Project #1, node ID: PVT_kwHODZU1As4Bkdhe), 27 ProjectV2Item entities were successfully created and could be individually retrieved using their unique node IDs. Each direct lookup confirmed the items' association with the correct project, their unarchived status (isArchived = false), and expected custom field values, including "Canonical ID". Six of these items were issue-backed, while the remaining 21 were draft items, all behaving as expected when accessed directly.

When Collections Come Up Empty

The core of the problem emerged when attempting to query these items as a collection. Despite the clear evidence of 27 existing items, any attempt to list them using collection-based methods, such as the GitHub CLI, consistently returned zero items. This directly impacts the ability to get a comprehensive overview of repo activity and project progress through standard tooling.

For instance, the command line interface query:

gh project item-list 1 --owner soonthorn707 --limit 100 --format json

yielded the following result:

{
  "items": [],
  "totalCount": 0
}

This stark contrast between direct node lookup and collection queries presents a significant challenge for project managers and developers relying on GitHub Projects V2 for accurate project visibility and reporting. Such a bug can severely hinder the effectiveness of software performance measurement tools and overall project oversight, as critical tasks or issues might effectively become "invisible" to automated processes or dashboard views.

Impact on Development Productivity

A bug of this nature can have a cascading effect on team productivity. If items are not correctly aggregated and displayed in collections, teams might:

• Struggle to get an accurate, real-time overview of project status.
• Miss critical tasks or issues that are present but not visible through standard project views.
• Experience difficulties in generating reports or integrating with other development productivity tools that rely on collection-based data.
• Spend valuable time manually verifying item existence, rather than focusing on development work.

The Community Response

The initial response to soonthorn707's report was an automated message from github-actions, acknowledging the submission of product feedback. While this confirms the report has been received by GitHub's product teams, the discussion itself did not provide an immediate solution, workaround, or a timeline for a fix. This highlights the ongoing need for community vigilance and reporting of such issues to ensure the continuous improvement of GitHub's core features.

For users encountering similar discrepancies, it's crucial to provide detailed evidence, including project IDs, item IDs, and the specific queries used, to help GitHub engineers diagnose and resolve these issues efficiently. Keep an eye on the GitHub Changelog and Product Roadmap for updates on fixes and enhancements to Projects V2.