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

Update: 2026-05-07 - delete+re-add cycle does NOT fix the forward index

Environment: HOUSEI-INC org, Project #8 (org-level Projects v2)

Root cause observation:

• Issues Allow For Multiple Answers To Be Marked as Answer #9-wLicense #21 were added via addProjectV2ItemById during a ~2-minute burst (05:31-05:32 UTC, coinciding with the service degradation window)
• All mutations returned success, but items never appeared in the project forward index
• Reverse query (issue -> projectItems) correctly shows all items linked to Project Allow for custom notifications for only when a discussion is answered #8
• project.items{totalCount} returns 7 (only items added before the degradation window)

Recovery attempt today:

1. Deleted each of the 13 missing items (deleteProjectV2Item) - OK
2. Re-added each item (addProjectV2ItemById) - OK, returned new itemIds
3. Re-set all 5 field values - OK
4. Verified via reverse index: all 13 items show project8 link - OK
5. Verified via forward index: totalCount still = 7 - FAIL

Conclusion: Forward index for this project is stuck/corrupted and cannot be repaired by delete+re-add cycles. A server-side index rebuild is required.

Related: orgs/community/discussions/193193 (same date/window), orgs/community/discussions/188487 (March regression, same fingerprint)