Project V2: addProjectV2ItemById succeeds but items never persist — account-wide, affects both API and UI

[Venture-Orient]

Problem

Cannot add ANY new items to any Project V2 board on my account. The addProjectV2ItemById GraphQL mutation returns success, but items never appear in the project's items list or the board UI. Existing items (added weeks ago) still work fine.

This affects both the API and the web UI — items appear briefly in the UI then vanish on refresh.

Account Details

• Personal account (not org), GitHub Free plan
• Private repository
• Project Welcome to GitHub product feedback #1 with 28 existing items (working)
• All project workflows disabled (tested with and without)

Evidence

1. Mutation succeeds but items list 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

2. Item node exists but is invisible to the project

# Direct node query FINDS the item:
query { node(id: "PVTI_lAHODV8Ajs4BQSPCzgmgSGg") {
  ... on ProjectV2Item { id isArchived content { ... on Issue { number } } }
}}
# Returns: isArchived=false, number=33, exists on the project

# Issue side also confirms association:
gh issue view 33 --json projectItems
# Shows: [{"status": {"name": "Todo"}, "title": "Venture Orient"}]

3. Brand new project board also fails

Created a fresh project, added 29 issues via mutation — all returned success. totalCount: 0. The problem is account-wide, not specific to one project.

4. Issue timeline confirms add/vanish cycle

added_to_project_v2      (Venture-Orient, 20:57:44)
project_v2_item_status_changed (github-project-automation[bot], 20:57:46)
... item vanishes from items list and UI ...

This cycle repeated 5+ times across API and UI attempts.

5. Web UI behavior

Clicking "+ Add item" → searching for issue → adding it → item appears briefly in the column → disappears on the next render/refresh.

What I've Ruled Out

• Not an item limit — project has 28 items, limit is 1,200+ (50,000 in preview)
• Not a workflow issue — all project workflows disabled, same behavior
• Not an issue body size problem — tested with a 1-line body, same result
• Not a specific issue problem — tested with multiple issues including a brand new test issue
• Not a token scope issue — token has project scope, and the UI (no token) also fails
• Not a repository issue — repo is properly linked to the project

Impact

• Cannot add new issues to project board
• Lost a previously-working item (Allow any emoji when creating the spotlight (including different skin tones) #32) after removing and trying to re-add it
• Project management workflow blocked

Expected Behavior

Items added via addProjectV2ItemById or the UI should appear in projectV2.items and remain visible on the board.

Environment

• GitHub Free plan, personal account
• Private repository
• Tested via gh CLI v2.45.0 and web UI
• Date: March 2, 2026

[kpanko-island]

Looks similar to me: #188486

[Venture-Orient]

Identical issue reported in #188486 by another user on the same day (March 2, 2026) — same symptoms with an org project and a PR instead of a personal project and issues. Appears to be a platform-wide regression in the project items indexing layer, not account-specific.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[Venture-Orient]

Resolved — the bug self-resolved approximately 1.5 hours after first occurrence. All items (including ghost items from multiple add attempts) are now visible on the board with correct field values. No action taken on our end — it cleared on its own.

Likely related to the PR incident that was active at the same time.

[cybulak]

Heads up that this one seems to be back. Hit exactly the same thing on my personal Project V2 today (April 20, 2026), roughly 7 weeks after your original report.

Setup is a single-user personal project with one private repo linked, nothing exotic. All 7 built-in workflows enabled including "Auto-add to project".

What triggered it, as far as I can tell: during a troubleshooting session I ran a bunch of GraphQL mutations on the same handful of issues in about a 30 minute window. Added an issue via addProjectV2ItemById, deleted it, re-added it, closed the issue, created a duplicate issue, added that one, closed it again, created a third one, and finally added it via the web UI sidebar. Standard stuff, nothing unusual about any individual step.

Every single mutation returned success with a fresh item ID. But every single item created during that 30 minute window has stayed invisible in project.items(first: 100). Items created before the window show up fine. Items created after the window, about an hour later through the web UI, also show up fine. Just that specific batch is stuck.

The odd part is that the data is clearly there. When I query it from the issue side, repository.issue(N).projectItems returns the item with isArchived false and the correct project id. But when I query the same project from the other direction, project.items(first: 100), totalCount does not increment and the item is missing from the node list. So it is not a pagination thing, it is not an archived thing, the row just never lands in the inverse index.

Workarounds I tried that did not help:

• Multiple rounds of deleteProjectV2Item plus addProjectV2ItemById. Same result every time, new item ID, still invisible.
• Toggling a label on the issue to wake up the "Auto-add to project" workflow. Workflow silently does nothing, even though the API reports it as enabled.
• Closing the affected issue and creating a fresh one with identical title, body and labels. The fresh issue also becomes invisible if I touch it during the affected window.
• Waiting. Your case self-resolved after about 90 minutes, mine is past 3 hours with no change.

One thing that did help, partially: opening the default Table view in the web UI and manually clicking "+ Add item" on the affected issue made it show up in that one view. But the API still does not see it from the project side, so any automation depending on project.items stays broken.

My best guess is a stuck materialization for a specific batch of items rather than something breaking at mutation time. The write path works, it's the inverse index that is not catching those rows, and the usual eventual-consistency path is not kicking in.

Happy to share API response JSON or screenshots if someone on the team wants to look.