GitHub Projects V2 items exist by direct node lookup but all project item collections return 0

[soonthorn707]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Projects

Body

Problem

I have a GitHub Projects V2 project where 27 ProjectV2 items were created successfully and can still be read directly by node ID, but every project item collection reports 0 items.

Account / Project

• User: soonthorn707
• Repository: soonthorn707/project6-ai-production-os
• Project: Project 6 — Roadmap
• Project number: 1
• Project node ID: PVT_kwHODZU1As4Bkdhe
• Project visibility: Private

Direct item evidence

There are 27 known ProjectV2Item IDs.

All 27 direct node reads successfully resolve and report:

• project.id = PVT_kwHODZU1As4Bkdhe
• isArchived = false
• expected Canonical ID custom field values
• 6 items are Issue-backed
• 21 items are Draft items

All 27 have the expected Project ID and Canonical ID.

Issues #1 through #6 also independently report Project membership in Project #1 and match the expected ProjectV2Item IDs.

Collection reads return zero

GitHub CLI:

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

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

### Guidelines

- [X] I have read the above statement and can confirm my post is relevant to the GitHub feature areas [Issues](https://docs.github.com/en/issues/tracking-your-work-with-issues/about-issues) and/or [Projects](https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects).

[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. ⭐