Organization Discussions not showing older discussions

[MegaPiggy]

Discussion Type

Bug

Discussion Content

For my organization discussions, none of the pages are showing anything. They only show discussions with recent activity from about the last 2 weeks.
https://github.com/orgs/ow-mods/discussions
https://github.com/orgs/ow-mods/discussions/categories/comments

However they do all appear with this specific link
https://github.com/orgs/ow-mods/discussions?discussions_q=

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

[TongyiDai]

This is reproducible and the URL difference identifies the problem. The default organization Discussions page currently injects is:open into the search field; ?discussions_q= clears that implicit filter. On ow-mods, the empty-query page shows pagination and older entries, while the default view shows only the 11 open discussions. GraphQL confirms the same inventory: 11 open, 0 closed, 11 total.

So the older discussions are not missing from storage. They are being omitted by the default is:open view even though they are also open. That makes this a listing/search UI inconsistency, not an archive or permissions issue. Category pages show the same behavior: the default URL includes both is:open and the category qualifier, while adding an empty discussions_q exposes more results.

The current workaround is to bookmark https://github.com/orgs/ow-mods/discussions?discussions_q= (and the equivalent category URL). For GitHub staff, the minimal reproduction is simply those two URLs plus the visible search-field values; no organization data needs to be changed.

[MegaPiggy]

Got tired of waiting, so we ended up closing and reopening all of the affected discussions, which seems to have fixed them. So unfortunately it may not be reproducible on our org anymore, but closing/reopening them was the workaround that restored everything.

[TongyiDai]

That workaround is useful diagnostic evidence. Closing and reopening appears to have forced GitHub to reprocess the affected discussions for the organization listing/search index; it does not look like the discussions were actually missing from storage.

I would not recommend close/reopen as a general fix because it changes state and may generate notifications. If this recurs, leave at least one affected discussion untouched and record:

• its discussion URL and ID;
• the default organization/category URL that omits it;
• the equivalent URL with ?discussions_q= that includes it;
• the UTC time the listing first became wrong.

That would preserve a live reproduction for GitHub. For now, it is still worth leaving this report open and adding that close/reopen rebuilt the listing, because that narrows the likely fault to indexing or cached query state rather than permissions or archival. Glad it restored the organization view.

[laymonage]

This issue started happening in August and they still haven't fixed it apparently. I first reported it here: https://github.com/orgs/community/discussions/202590