GitHub Project V2 Items Vanishing Act: A Community Insight into Persistence Issues

GitHub Project V2 Items Vanishing Act: A Community Insight into Persistence Issues

In the fast-paced world of software development, reliable tools are the bedrock of developer productivity. So, when a core feature like adding items to a project board falters, it can bring workflows to a grinding halt. Recently, a GitHub user, Venture-Orient, highlighted a critical bug in GitHub Project V2 where newly added items would inexplicably vanish, impacting both API and UI interactions.

The issue, reported on March 2, 2026, described a scenario where the addProjectV2ItemById GraphQL mutation would successfully return an item ID, yet the item would never persist in the project's item list or the board UI. Existing items remained unaffected, but any new additions would briefly appear before disappearing on refresh. This wasn't an isolated incident; it was an account-wide problem, affecting multiple projects and even brand-new boards.

The Evidence: Success Without Persistence

Venture-Orient provided clear evidence of the bug, demonstrating that while the GraphQL mutation succeeded, the item count remained unchanged:

# This succeeds and returns an item ID: mutation {   addProjectV2ItemById(input: {     projectId: "PVT_kwHODV8Ajs4BQSPC"     contentId: "I_kwDORWXr9c7vNbTT"   }) {     item {       id     }   } } # Returns: {"item": {"id": "PVTI_lAHODV8Ajs4BQSPCzgmgSGg"}}  # But the items list never includes it: query {   user(login: "Venture-Orient") {     projectV2(number: 1) {       items(first: 50) {         totalCount       }     }   } } # totalCount stays at 28 — never increments

Further investigation revealed that the item node *did* exist when queried directly, confirming its creation, but it remained invisible to the project's item list. The web UI mirrored this behavior: items would appear briefly in a column only to disappear on the next render or refresh. Even the issue timeline showed a perplexing "added_to_project_v2" event followed by a "project_v2_item_status_changed" by the automation bot, after which the item would vanish.

Troubleshooting and Community Confirmation

Venture-Orient meticulously ruled out common culprits:

• Not an item limit: The project had only 28 items, far below the 1,200+ limit.
• Not a workflow issue: All project workflows were disabled.
• Not content-specific: Tested with various issues, including a brand new one.
• Not a token scope or repository issue: The token had appropriate scope, and the UI (which doesn't use a token) also failed.

Crucially, another user reported an identical issue (#188486) on the same day, suggesting a platform-wide regression rather than an account-specific problem. This kind of shared experience underscores the value of community insights for identifying systemic issues.

Resolution and Impact on Developer Productivity

Approximately 1.5 hours after its initial occurrence, the bug self-resolved. All previously "ghost" items, including those from multiple failed attempts, became visible on the board with correct field values. No action was taken by the user, indicating a backend fix or system stabilization, likely related to other active incidents at the time.

While self-resolving, such incidents highlight the fragility of relying solely on a single platform for critical project management. For teams seeking a robust Sourcelevel alternative or even a Haystack alternative for deeper insights into their development workflow, reliability in basic operations is non-negotiable. When developers cannot trust that their project updates will persist, it directly impacts their ability to plan, track, and collaborate effectively, leading to lost time and decreased productivity. This incident serves as a reminder that even the most advanced tools can experience hiccups, and having resilient workflows and potentially backup strategies is vital for sustained developer activity.