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.

[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

[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 :)

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

[paulfenney]

Our project was reindexed 2 weeks ago but we are still experiencing new instances of this problem. Is there a known issue?

[kulathilake]

Had the same issue. (Issue created from within the project and associated with a repo). The issue didn't show up in any of the views, with multiple combinations of slicing & swim lanes tried out. However, it did appear in the project after the project association was removed from the issue (within the repository) and re-added to the project through the add item option (Add item from repository)

[paulfenney]

This sounds similar to my experience. Removing and re-adding by any method seems to fix it, but we need to be able to rely on issues being visible on the board automatically!

[ReubenJ]

Having the same issue, but removing from the project via the issue's page and re-adding via the "add item" option is no longer working either.

[tamaraassisb-cmd]

Thank you!! You just fixed my problem! I hope you were able to fix yours

[Trungmaster5]

The issue remains.

[ATNekma]

Same here, it desorganised my team completely

[cthunman]

Just hit the same issue.

[chrismoseley]

Yep, also seeing this today.

[javi-alzorriz-camunda]

same issue too. No solution yet?

[cthunman]

Looks like this is probably related: https://www.githubstatus.com/

[eeeeebader]

I suddenly also have the problem. the workaround (that I remove the issue from the project and then add it again by import issues using the "Add item from repository" function) works but it is definitely a bug.

[nene]

Thanks, this workaround worked for me as well. I too started to experience this problem just today. Never happened before.

[eeeeebader]

Hi @nene. maybe you can also follow the bug report as proposed by @syedahmedx3. I will update my comment if that worked.

[nene]

Sorry, I have no idea what you're referring to. From where do I find that bug report?

[eeeeebader]

search in the thread the name syedahmedx3 syedahmedx3. it is in a green box at the very top

[nene]

OK. Thanks for the clarification. Anyway.. in the mean time things started to work again without me taking any further action. I think you meant to write "file a bug report" not "follow the bug report". I ended up not following or filing any bug reports.

[nbarsova]

Still experiencing this.

[finlayiainmaclean]

Still seeing this

[Firrow]

I had the same problem 4 hours ago, and I'm having it again right now

[samus-aran]

Hi everyone, we appreciate you reaching out to report this issue! 

We have provided details about the incident in this discussion. Please subscribe to that post to receive real-time updates and a notification when the incident is resolved. 

If you have further questions or additional details about your experience, please comment directly on the discussion linked above.

We appreciate your patience as we work toward a solution.

[lunamoonmoon]

Experiencing this, issue is in repo but doesn't show on project board even though that is where issue was created. Cannot add from repository from board as it doesn't show in list there.

[chrismoseley]

They're gradually fixing it but the workaround is to go directly to the issue (from issues), move it out of the project, then it will appear in the "add from repository" list.

[lunamoonmoon]

Okay got it to work, took quite a while as I tried creating a 2nd ticket and moving status ect. Solution for me was completely un-attaching from project then re-adding from repository on the project board and for some reason it worked.

[lunamoonmoon]

Thank you @chrismoseley !

[monancho]

Hi GitHub team - please investigate or reindex a user-owned Projects v2 project affected by the current stale-Projects incident (8zc63m64hy36).

Project: https://github.com/users/monancho/projects/2 (node PVT_kwHOCnRQ6s4BkXGq)
Repository: https://github.com/monancho/github-workflow
Affected issue: monancho/github-workflow#56

As of 2026-09-23 16:48 UTC, the Issue-to-Project GraphQL connection and direct REST item GET both return active item PVTI_lAHOCnRQ6s4BkXGqzg8V09A (REST item 253088720), isArchived=false, with Status=In Progress, Scope Origin=Added, Estimate=2. But user.projectV2(number:2).items(first:100) and GET /users/monancho/projectsV2/2/items?per_page=100 return 31 items and omit #56; 32 are directly associated. Saved Release Overview has 29/30 release Issues, Added Scope 0/1, and Attention 0/1 despite #56's blocked label. All visible Project items are Issue content; #56 has no PR.

Issue #7 had the same mismatch and became visible later without deletion, suggesting delayed recovery. Idempotent add attempts returned the original item or Content already exists in this project; updating the existing field values did not repair the forward list. We preserved both original item IDs and values.

Recent GitHub request IDs at 16:48:16 UTC: direct #56 item GET F13A:A88AC:15BBC:2125E:6AB402D0; Project list GET F139:25A510:169F1:2230C:6AB402D0. Full minimal reproduction and prior request IDs are recorded in public tracking issue #56, especially monancho/github-workflow#56 (comment).

Could GitHub reindex this Project or confirm the incident's backfill will include item #56? Please advise a supported recovery path. We are avoiding delete/re-add because other reports in this thread show it can lose item history without fixing the index.

[monancho]

Update (2026-09-23 22:29 UTC): This Project recovered without deleting or recreating any items. The forward item list now includes all 32 expected items, including the original #56 item. Saved Release Overview and Hierarchy each return 30/30 release Issues, Baseline Progress 24/24 leaves, Added Scope #56, and Attention showed #56 while it still had the blocked label. We removed the blocker and closed the tracking issue after verification. GitHub incident 8zc63m64hy36 remains investigating; we cannot establish whether our report or incident backfill caused the recovery. No account-specific reindex action is currently needed. Thank you.

[monancho]

New related occurrence (2026-09-23 22:47 UTC): After the original Project #2 recovered, an independent public pilot repo was provisioned: https://github.com/monancho/github-workflow-v010-pilot-20260924-a . Its new dedicated user Project #4 (https://github.com/users/monancho/projects/4, node PVT_kwHOCnRQ6s4BkfD3) has an active, unarchived direct Issue #1 item PVTI_lAHOCnRQ6s4BkfD3zg8brJ4. The Issue-side projectItems connection and direct item read succeed; Status is Done after the linked PR merged. But the Project #4 forward item list returns 0 items. A separate test-created unrelated Project #3 also has an active direct draft item but returns 0 forward-list items. Project #4 REST list request ID ED30:2B0393:829F8:D7ACA:6AB456F1; direct GraphQL item request ID ED33:E2DF9:848C1:D9A34:6AB456F1 (same minute). We have not deleted/re-added either item. Could the incident backfill cover these newly created user Projects too? This blocks final pilot Project-list acceptance even though direct reads and the provisioner verify pass.