GitHub Projects v2 Glitch: When 'git software' Commands Don't Reflect on Your Board

In the fast-paced world of software development, reliable tools are the bedrock of developer productivity. When core git software like GitHub's project management features don't behave as expected, it can quickly derail planning and tracking efforts. A recent discussion on the GitHub Community forum sheds light on a particularly frustrating bug impacting Projects v2, where items appear to be added successfully but remain invisible on the project board.

The Invisible Item Bug in GitHub Projects v2

Community member MadsBuus brought attention to a critical issue: using the gh CLI to add an issue to an org-level Project v2 reports success, and the issue itself shows the correct project association, but the item never actually appears in the project's item list or on the board. This isn't just a display glitch; it fundamentally breaks the project tracking workflow.

The Problem in Detail

The core of the bug manifests in several ways:

• CLI Success, UI Failure: After executing

  gh project item-add --owner  --url https://github.com///issues/

  , the command indicates success. However, a subsequent check with

  gh project item-list --owner  --format json

  reveals the newly added issue is missing. The issue itself, when viewed via

  gh issue view --repo / 

  , correctly displays the project association.
• Auto-Add Workflow Failure: An auto-add workflow configured with a filter like is:issue for newly created issues in linked private repositories also fails to trigger, leaving new issues unassigned to the project.
• UI Search Limitations: When attempting to add items via the web UI's search function within the project, only pull requests from the linked private repositories are returned, not issues.

This behavior suggests a disconnect between the API reporting success and the actual persistence or indexing within the Project v2 system. The discussion author noted a "fingerprint matches #188487 (resolved March 2), suggesting a possible regression again," indicating this might be a recurring issue.

Impact on Developer Productivity and Sprint Planning

For teams relying on GitHub Projects for their sprint planning and daily stand-ups, this bug is a significant blocker. Imagine a scenario where a critical bug fix or feature task is "added" to a project, but never appears on the board. This can lead to:

• Missed tasks and delayed work.
• Confusion and wasted time manually verifying project item lists.
• Erosion of trust in project management tools.
• Difficulty in accurate engineering statistics gathering if items are not correctly tracked.

The ability to seamlessly integrate issues and pull requests into project boards using efficient git software commands is crucial for maintaining flow and visibility. When these integrations break, developers spend less time coding and more time troubleshooting their tools.

Seeking Solutions and Community Insights

As of the discussion, no immediate solution or workaround was provided by GitHub staff, beyond the automated feedback acknowledgment. However, another community member, cbaeberle, linked to Discussion #193185, suggesting that this might be a known or related problem. This highlights the value of community discussions in identifying and escalating such issues.

If you've encountered similar challenges with GitHub Projects v2, particularly with items not appearing after being added via the CLI or auto-add workflows, sharing your experience on the GitHub Community forum is vital. Your input helps product teams prioritize fixes and ensures that essential git software tools continue to support, rather than hinder, developer productivity.

You can follow the original discussion here for any updates.