Milestone shows 80% completion although all five assigned issues are closed

[dwinx00]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Issues

Body

The milestone progress summary disagrees with its assigned issue states.

Repository: https://github.com/dwinx00/SAFE_Dashboard
Milestone: https://github.com/dwinx00/SAFE_Dashboard/milestone/1

Actual issue states

All five assigned issues are closed as completed:
#36, #38, #52, #56 and #59.

Incorrect summary

The milestone displays:

• 80% complete
• 1 open issue
• 4 closed issues

The REST API query for open issues returns an empty list:
https://api.github.com/repos/dwinx00/SAFE_Dashboard/issues?milestone=1&state=open

However, the milestone metadata returned with assigned issues reports:

• open_issues: 1
• closed_issues: 4

Expected result

0 open issues, 5 closed issues and 100% completion.

Browser refreshing did not resolve the discrepancy. Screenshots are attached.

Could GitHub investigate and reconcile the milestone counters?

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

[mohdkhatab]

Your own evidence already rules out the simple explanations, and it points to the right diagnosis: the milestone's stored counters are out of sync with its actual issue list. Refreshing does not fix it because the page is not showing stale browser data — it is faithfully showing stale counters (4 closed / 1 open = 80%, which is internally consistent, just wrong).

Milestone counters on GitHub are stored fields (open_issues / closed_issues on the milestone object), not computed live from the issue list every time the page loads. They can go stale when an issue assigned to the milestone is reopened and closed again, transferred between milestones, or when a pull request is added to or removed from the milestone. That is why the REST query for open issues returns an empty list while the milestone metadata still says open_issues: 1: the two are reading different sources.

Before escalating, check for a "phantom" sixth item, because milestone progress counts pull requests as well as issues:

1. Query the milestone with state=all, not just state=open: GET /repos/dwinx00/SAFE_Dashboard/issues?milestone=1&state=all (and the same via the milestone endpoint, GET /repos/dwinx00/SAFE_Dashboard/milestones/1). List every returned item and its state. If you see a pull request assigned to this milestone, that is your missing item — PRs count toward milestone progress even though they are easy to miss when you are only looking at the five issues you listed.

2. If the state=all list really is only your five closed issues, try forcing a recount: remove the milestone from one issue and re-add it, or edit the milestone (for example, change and then restore its description). Either action often triggers GitHub to recompute the counters.

3. If the counters still say open_issues: 1 after that, this is a server-side counter bug that the community cannot fix from the outside. Report it to GitHub Support with exactly the evidence you already gathered: the milestone URL, the GET /milestones/1 response showing open_issues: 1, closed_issues: 4, and the empty state=open issues query. That combination proves the discrepancy is in GitHub's stored counters, not in your browser or your issue states, and it is what Support needs to reconcile the milestone.

[dwinx00]

Confirmed: the state=all query returns only the five closed issues, with no pull requests. The open query is empty, but milestone metadata still reports 1 open and 4 closed. I have not tried changing assignments or editing the milestone.