[Projects] Issue added to a Project (v2) does not appear on the board or in the items list until later; Changing its Status makes it show up on the board

[akpmohan07]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Issues

Body

What happens
After adding an issue to a user-owned Project (v2), the item is not visible on the board. It is a member of the project according to the issue itself, but the project's own item list does not include it.

Steps to reproduce

1. Create an issue in a public repository.
2. Add it to a user-owned Project (v2). I tried both the web UI and the CLI (gh project item-add <number> --owner <owner> --url <issue-url>, gh 2.87.2). Same result both ways.
3. Open the project board. The item is not there.
4. Set the item's Status field (single select). The item now appears on the board.

What I checked through the API (GraphQL)

• The issue's projectItems lists the project, isArchived: false.
• A direct lookup of the item by its node id returns it, in the project, with the Status I set.
• The project's items connection (and gh project item-list) does not include it: totalCount stayed at 7 while 2 new items had been added.
• Several minutes later one of the two items had appeared (totalCount 8) and the other, added earlier, still had not. So it is inconsistent, not simply first-in-first-out.

Expected
A newly added item shows up on the board and in the items list right away, whether or not it has a Status.

Environment
Project (v2) owned by a user account, public repo, browser UI and gh 2.87.2 on macOS. Date: 2026-09-24.

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or 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. ⭐

[lucapivato]

I have the same issue, in all projects. But setting the status or removing it doesn't change anything. I just added 3 issues with identical properties and only 1 is visible in the project. The other 2 are not visible and if I try to add them again it says they are already in the project. Tried all views and removed all filters, the issues are not visible.

Has been happening for a while now. After about 10 minutes they start appearing in no particular order.

[akpmohan07]

I tried changing the status on the issue page.

My thought:
They may have two different services with two persistent DBs,
Issue
Projects

It is an eventual consistency issue,
They may sync via triggers on events (CRUD) or on a schedule.