New issues disappearing from all projects and not visible in any view. Still show in Repo.

[DevBehringerDE]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Issues

Body

Inside the projects, after creating a new issue that you would be able to see, and then after a few seconds or after you reload the page, it disappears. The added issue will show up in the repo, however is completely absent from the project. This issue persists across all projects and all repos. Any support would be appreciated!

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

[nk-spr]

Experiencing the same issue, GitHub Project Automation is also not working for these tasks.
Adding issues directly to Board works but any further changes will result in same error.

[morten-knud-nielsen]

Experiencing the same!

[keesverweij-oakk]

also!

[afmg-aherzog]

Here as well. Kind of makes my teams work harder.

[NickVolynkin]

Same.
A similar problem was reported earlier in https://github.com/orgs/community/discussions/169602

[hcnp]

Same.

[mirceabratu]

same wtf

[Ingo24]

same problem

[janpowaga]

same

[FredericFouche]

Same problem over here

[ken-mellem]

Same

[bulutkorzay-fm]

Same

[Jianbe-03]

New issues also not appearing for me, i can only see a single issue not more.

[gregoireverweijen]

Same, For me it seems that the default status is no longer applied.

[gregoireverweijen]

For me this works again for new issues. For existing issues I had to re-apply the project to make the issues appear on the board. Even if you manually set the status before (it wasn't showning then) it still won't appear on the board until you re-apply the project.

[sdepouw]

Based on this comment, I gave it a go, and I'm also seeing this improvement:

• Cards created during the 'downtime' have to be removed from the Project and re-Added
• Once done, they will now start appearing on the Project board / views correctly

[DevBehringerDE]

For me this works again for new issues. For existing issues I had to re-apply the project to make the issues appear on the board. Even if you manually set the status before (it wasn't showning then) it still won't appear on the board until you re-apply the project.

Nice, same here. Thanks for that update :)

[HangyBoi]

I have the same issue right now. Glad to see that I am not the only experiencing this, and that this thread has revived again lol

[HangyBoi]

Have tried removing/reassign the project again to the issue - doesn't appear on the board anyway.

[samuelemusiani]

Same, removing/reassign does not work for me

[akshttdev]

Also experiencing the same issue now. Feeling relieved that I am not alone here.

[LTCatt]

Me too...

[eemuston]

This is happening for me too. Thank god the issues are saved to the repo because I only noticed this now.

[steve-crouch]

Seeing this also. Added 6 issues to a repo assigned to a board, only 4 appeared on the board. Reassigning the project didn't work.

[vibav-ph]

The team members in our org were facing the same issue now. Thought that there are some hidden filters that's causing it, but just stumbled upon this thread.

[tinylion1968]

same issue here. all of todays issues created not displaying. either created on the github site, or through our api tools.

this has also made our api fail with a reported overuse. but the overuse was triggered by the api not returning our new list of issues. so now im temp locked out also.

this is a problem here

the issues are showing in the All issues list view, but not in the tabbed project issues pages, and todays issues weren't being return via the api to our tools

edit:
looks like an issue with graphql rate limit failing our api calls
did a limit report to check usage and as you see below all should be well but calls are failing with rate overuse

api call returned: `rate limit already reached...etc`


── GitHub API Rate Limit Report ─────────────────────────

  Bucket      Limit    Used   Remaining   Reset
  ──────      ─────    ────   ─────────   ─────
  core         5000       0        5000   1:28:27 PM
  graphql      5000       0        5000   1:28:27 PM
  search         30       0          30   12:29:27 PM

── Session Summary ─────────────────────────────────────

  Session uptime:    00:17:26
  Total API calls:   17
  Total errors:      6
  Total retries:     0
  Tripwire events:   5

  Calls by bucket:
    core: 10 calls (avg 305ms)
    graphql: 7 calls (avg 299ms)

── Tripwire Events ─────────────────────────────────────

  [CAUTION] graphql remaining: 41 — approaching limit (graphql)
  [CAUTION] graphql remaining: 41 — approaching limit (graphql)
  [CAUTION] graphql remaining: 41 — approaching limit (graphql)
  [CAUTION] graphql remaining: 40 — approaching limit (graphql)
  [CAUTION] graphql remaining: 16 — approaching limit (graphql)

── Recent Calls (last 17) ────────────────────────────

  11:11:04  POST   /graphql                                   ProjectIssuesProvider._resolveOwnerType 200   336ms  [41/5000]
  11:11:04  POST   /graphql                                   ProjectIssuesProvider._fetchProjectItems 200   300ms  [41/5000] ✘
  11:11:07  POST   /graphql                                   ProjectIssuesProvider._fetchProjectItems 200   250ms  [41/5000] ✘
  11:11:16  GET    /rate_limit                                getRateLimitStatus        200   317ms  [5000/5000]
  11:11:34  GET    /rate_limit                                getRateLimitStatus        200   285ms  [5000/5000]
  11:11:44  POST   /graphql                                   ProjectIssuesProvider._fetchProjectItems 200   282ms  [40/5000] ✘
  11:14:01  GET    /rate_limit                                getRateLimitStatus        200   327ms  [5000/5000]
  11:17:38  POST   /graphql                                   ProjectIssuesProvider._fetchProjectItems 200   334ms  [16/5000] ✘
  11:18:28  POST   /graphql                                   ProjectIssuesProvider._fetchProjectItems 200   279ms  [0/5000] ✘
  11:19:44  GET    /rate_limit                                getRateLimitStatus        200   280ms  [5000/5000]
  11:25:28  GET    /rate_limit                                getRateLimitStatus        200   289ms  [5000/5000]
  11:25:39  GET    /rate_limit                                getRateLimitStatus        200   311ms  [5000/5000]
  11:25:55  POST   /graphql                                   ProjectIssuesProvider._fetchProjectItems 200   315ms  [0/5000] ✘
  11:25:59  GET    /rate_limit                                getRateLimitStatus        200   314ms  [5000/5000]
  11:27:36  GET    /rate_limit                                getRateLimitStatus        200   325ms  [5000/5000]
  11:27:53  GET    /rate_limit                                getRateLimitStatus        200   302ms  [5000/5000]
  11:28:30  GET    /rate_limit                                getRateLimitStatus        200   301ms  [5000/5000]

[MamduhKod]

Same issue here.

1 of 4 issues (created today) shown in the board so far.

[grendes-wunder]

Same issue here!

[kahlus2001]

this issue is here again - same issue accross 2 different gh organizations and on all repositories

[sorokin-vladimir]

same issue

crete new one in a Project -> refresh page -> don't see the task (issue)

[GET-Paul]

Problem just started here today as well. Issue only reappeared once closed and a random amount of time passed.

The issues are listed on the Repository, and also when adding a 'Closes #' PR line in Visual Studio just fine.

[simogilaa]

Same issue, happens both if i create the issue directly on the project screen (kanban style) and if i create the issue from the "Issues" page and manually assign a project + status. Card is there until the first refresh or action (eg. moving it anywhere inside the column or to another column)

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