Closed milestone page shows unrelated open pull requests #202700
Replies: 2 comments
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
Screenshot taken from the affected milestone page. It shows |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Issues
Body
Summary
The milestone detail page for a closed milestone displays open pull requests that belong to a different milestone.
Public reproduction
Repository: https://github.com/binarywang/WxJava
Affected milestone: https://github.com/binarywang/WxJava/milestone/99 (number 99, title
4.8.5, closed)The page defaults to the Open tab and shows these six open PRs:
However, each is assigned to milestone 4.8.6, not 4.8.5. The milestone itself has zero open items.
Expected behavior
The Open tab for milestone #99 should show no items, because no open issue or PR is assigned to that milestone.
Actual behavior
The Open tab shows the repository's six currently open PRs even though none is assigned to milestone #99.
Evidence
GET /repos/binarywang/WxJava/milestones/99reportsopen_issues: 0.GET /repos/binarywang/WxJava/issues?milestone=99&state=openreturns no items.state:open milestone-number:99 archived:false sort:milestone_prio-desc, but the result contains the six PRs above instead.4.8.6in the REST pull-request response.This looks distinct from https://github.com/orgs/community/discussions/202166, which concerned milestone-assigned PRs missing from the page/API. Here the REST API and milestone counts are correct; the milestone page's Issues search result includes PRs assigned to another milestone.
Environment
Observed on github.com in Chrome on 2026-07-23 (UTC+08:00), both signed in and signed out.
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions