projects sub-issue progress shows 0/1 for epic issues despite multiple linked sub-issues

[trvswgnr]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Projects

Body

summary

in github projects, epic issue cards show sub-issue progress as 0/1 (0%) even when the epic has multiple linked sub-issues.

the underlying data appears inconsistent across apis:

• graphql issue relationships show correct sub-issue counts
• rest issue payload sub_issues_summary reports total: 1 for each epic

repo / examples

repo: https://github.com/trvswgnr/op

epics:

• Epic: Code Structure & Maintainability trvswgnr/prodkit#27 (has 3 sub-issues)
• Epic: Type Safety trvswgnr/prodkit#28 (has 2 sub-issues)
• Epic: Test Architecture & Coverage trvswgnr/prodkit#34 (has 8 sub-issues)
• Epic: Documentation trvswgnr/prodkit#43 (has 3 sub-issues)
• Epic: Build, CI & Release Process trvswgnr/prodkit#47 (has 2 sub-issues)

all sub-issues are open.

expected behavior

project card sub-issue progress should reflect actual linked sub-issue count, e.g.:

• Epic: Code Structure & Maintainability trvswgnr/prodkit#27 should show 0/3
• Epic: Test Architecture & Coverage trvswgnr/prodkit#34 should show 0/8
• etc

actual behavior

each epic shows 0/1 and 0% in the project view.

repro steps

1. create/open an issue to act as epic
2. link multiple child issues via github sub-issue relationships
3. open the github project board/list where the epic issue card is shown
4. observe sub-issue progress on card: shows 0/1 instead of 0/N

api evidence

graphql (correct counts):

• issue(number: 27).subIssues.totalCount = 3
• issue(number: 34).subIssues.totalCount = 8

rest (appears incorrect):

• GET /repos/{owner}/{repo}/issues/27 returns:
  • "sub_issues_summary": { "total": 1, "completed": 0, "percent_completed": 0 }
• same pattern for Epic: Type Safety trvswgnr/prodkit#28, Epic: Test Architecture & Coverage trvswgnr/prodkit#34, Epic: Documentation trvswgnr/prodkit#43, Epic: Build, CI & Release Process trvswgnr/prodkit#47

additional notes

• sub-issue links are valid and visible in issue relationships
• remove/re-add of all sub-issue edges did not trigger recalculation (still 0/1)
• this looks like a projects/sub_issues_summary computation mismatch rather than missing linkage

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