Development panel limits linked issues to 10 with no documented cap or error message

[MapticianNate]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Issues

Body

Description

The "Development" section in a pull request's sidebar silently stops accepting linked issues after 10. There is no error message, no indicator that a limit exists, and no documentation of the cap. The UI appears to accept the action but does not save the link. Is there a reason for this 10 issue limitation?

Steps to Reproduce

1. Open any pull request.
2. In the "Development" sidebar panel, link 10 issues.
3. Attempt to link an 11th issue.

Expected Behavior

Either the issue links successfully, or GitHub displays an explicit message stating that the Development panel has a maximum limit of linked issues.

Actual Behavior

The 11th link silently fails. No error is shown. The issue does not appear in the panel. The user has no indication that a limit was reached.

Additional Context

• Closing keywords in the PR description body do not appear to share this limit, which makes the behavior inconsistent across two native linking mechanisms for the same feature.
• The limit is not documented in GitHub Docs under pull requests or the Development panel.
• Workaround: use Closes #N keywords in the PR body description.

Impact

Teams that use issues to track bugs against a PR cannot reliably use the Development panel for PRs with more than 10 linked issues. Silent failure makes this difficult to catch and easy to misdiagnose as a UI glitch.

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

[ebndev]

Hi @MapticianNate thanks for posting in GitHub Discussions!

I've gone ahead and moved this post to our Pull Requests category, as this topic may be more relevant there and will ensure your feedback can be reviewed by the proper GitHub team.

[jamalkamaladdin]

Docs state this cap: manual links allow up to ten issues per pull request. Closing keywords in your PR description have no such documented cap. Keywords link only when your PR targets your default branch.

Docs: https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue