Issues not attaching to project

[pblackwood]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Projects

Body

Summary

Issues added to the one-and-only project in this repository are suddenly disappearing from the project views. This started occurring today (2026-04-20). Closing and reopening an affected issue caused another (previously working) issue to also disappear from the project.

Details

• Organization: SteelCityBg
• Repository: steelcitybg
• Project: MVP Tasks
• Affected Issues: #85, #86 (and possibly others)
• Timeline:
  • Before today: Could successfully add issues to the MVP Tasks project; issues appeared in project views as expected.
  • Today, 2026-04-20:
    • Issue #85 no longer appeared in MVP Tasks project views, even though it was linked.
    • Removing/re-adding the association did not help.
    • Creating a new issue (#86) and linking it to the project worked at first; the new issue appeared as expected.
    • Closing and reopening #85, then re-adding it to the project, caused both #85 and #86 to disappear from the project.
    • Now neither #85 nor #86 appears in the MVP Tasks project, even after relinking.

Troubleshooting Actions Attempted

• Checked and cleared all project view filters
• Tried different project views (table, board, etc.)
• Confirmed project is the new Projects type
• Removed/re-added project links on affected issues
• Successfully added and viewed numerous issues in the past (as owner)
• Attempted close/reopen workflow (issues disappeared after this)

Additional Context

• User is an organization owner with full permissions
• No "Save" button appears when adding a project from the issue UI
• No errors shown in UI
• Other issues may be missing after this event

Urgency

This appears to be a GitHub Projects data corruption or severe linking bug.

---

Steps to Reproduce:

1. Open https://github.com/SteelCityBg/steelcitybg/issues/85
2. Remove then re-add MVP Tasks from the "Projects" sidebar
3. Close and reopen the issue
4. Observe that linked issues (including new ones, e.g. #86) disappear from the project views

---

Please advise as soon as possible, as this is blocking project tracking and risks data loss.

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

[FDE-1]

same here

[idontsov]

We are experiencing the same issue.

[pblackwood]

Sorry to hear that, but happy to hear that. Maybe it will get someone's attention.

[syedahmedx3]

@pblackwood, did the support ticket work for you?
If this solved it,
marking it as answered would help the other 20+ people hitting this same bug find the fix faster.

[Jianbe-03]

Same issue here!

[TomHarveyInvida]

This is happening for us also.

Similar to this issue #169602

[probitaille]

Indeed, there are several people, including myself, who have searched for this problem and come across this old issue.

[uchusei]

Same issue here!

[obryckim]

Same. No new issues can be added to any of our projects.

When trying to manually add from the table view, only PRs are showing up.

[cbaeberle]

Same here.

[fpervaiz]

Same here, no workaround found yet

[egor-ulianov]

Same.

[probitaille]

I can see my new issues in the project repository but not in my Project Kanban

[verwema]

Same

[CJJeffery]

Having the same issue here

[DanielCamSan]

same here

[salomvary]

Meanwhile, I've tried reproducing the issue on a newly created project + public repo without luck. All seems to be fine there.

[Tguisnet]

Same

[dhenriet]

For me, it's back to normal, and I can see the issues again in the Backlog column and other columns.
It's really strange that some people are still having this issue.

[UmiKami]

I am still having this issue.

I tried changing the status of some of the issues to see if it forced the board to update but nothing.

Just now, I even tried to unassign the project in the issue, assign the project again. I get this log:

github-project-automation moved this to Backlog in Tower Defense Game1 minute ago

It is still not showing up on the board, not even after a hard refresh and clearing cache.

[aidar-darmenov-livatek]

Same issue here!

Other threads with the same problem:

• https://github.com/orgs/community/discussions/193193
• https://github.com/orgs/community/discussions/193194

[dhenriet]

Even though it's working for me now, it's actually really strange. I can still see the two issues from yesterday that were affected by the bug in the classic issue view. In board view, I don't see those two issues. I can see the ones created before and after them.
So I think there was a bug and that those two issues will never reappear.
But it's still surprising, given the number of bugs reported and comments, that we don't know more.

[FDE-1]

It seems to be working now. ¯\_(ツ)_/¯

[dominicafonso-datum]

btw https://www.bryanbraun.com/2020/11/06/using-the-shrug-emoticon-in-markdown/
or ¯\_(ツ)_/¯

[FDE-1]

Thanks

[Eric2-Praxinos]

Still not working for me.

[joerj123]

This is still flakey, slow and not fully working.
This seems wrong!
https://www.githubstatus.com/

[arnavpraneet]

Still not working for me

[jamesoflol]

same problem here

[FaultyFunctions]

Same problem still, it is extremely annoying trying to manage a project like this. I should just switch back to Trello, all the issues with projects is just ridiculous.

[FaultyFunctions]

I gave up and I'm using zenhub now.

[DakshChhokra]

Same here. Saw this issues all day on 4/27/26

[dhenriet]

It's probably because the GitHub maintenance is done with Opus 4.7 :)

[syedahmedx3]

This is a server-side index bug — here's what actually works:

Fix: Submit a support ticket at https://support.github.com/contact/bug-report with your org and project name. GitHub is manually reindexing affected projects on request — confirmed working in thread #193463.

Why nothing you've tried works: The issue data is fine on GitHub's backend (that's why the automation log says "moved to Backlog"), but the project view index is out of sync. Clearing cache, removing/re-adding the project link, and switching views all do nothing because it's a server-side problem.

Why close/reopen made it worse: Each write event compounds the index drift.

Verify your data is intact while waiting:

gh project item-list <project-number> --owner <your-org>

If your issues appear here, nothing is lost — it's purely a display bug.

[pblackwood]

Caveat: I didn't try the support ticket approach, because for me, the orgs & projects corrected themselves. I don't understand why some orgs & projects corrected and others didn't. But I appreciate the explanation.

[syedahmedx3]

Glad to hear yours synced back up!
It seems like GitHub is rolling out background fixes, but the index drift is definitely hitting different orgs at different speeds.
For anyone still blocked, that manual re-index ticket remains the most reliable 'force-fix.' Happy coding!