Feature request: Role-based Issues section access control

[ufukty]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Issues

Body

Requested feature

Ability for repository owners to manage accesses to a repository's Issues section based on the user role (eg. contributor, collaborator and member) and the access type (eg. read-only and read-write).

Need

1. This feature can enable sanitizing the Issues section from informal, poorly written (yet unavoidable) user reports by directing users into the Discussions section.
   • The Discussions section is better medium for community engagement than Issues as it supports avoiding context lost as it allows hierarchical threads.
   • It makes more sense to receive user feedback first in Discussions and officially opening one Issue per valid points as the users who have the crucial information are not obligated or forced to be bothered by following the style of repository and maintainers have better understanding of Issue policy of a repository than product users.
   • User post Issues clutter the Issues section and makes tracking relation between first party Issues harder.

Related

• Only allow issues to be created by contributors or people who have created pull requests dear-github/dear-github#293 is a similar feature request with 100 upvote.

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[Gecko51]

This doesn't exist at the repo settings level right now. The closest you can get natively is disabling issues entirely, or using issue templates with blank issues turned off. The second option is probably what you want:

.github/ISSUE_TEMPLATE/config.yml:

blank_issues_enabled: false
contact_links:
  - name: Community Discussions
    url: https://github.com/yourorg/yourrepo/discussions
    about: Questions, feedback, and informal reports go here

This removes the "Open a blank issue" option from the new issue page and lets you redirect people to Discussions. It doesn't technically block anyone from filing an issue via the API or direct URL, but it removes the friction for casual users who follow the UI flow.

For actual role-based access control scoped to the Issues section, that's a gap in GitHub's permission model right now. The org-level roles (triage, write, maintain) don't let you carve out Issues specifically. Your best bet is filing this at https://github.com/github/feedback with the Issues label and linking the dear-github thread as prior art, that one has serious history behind it and more upvotes will help move it.

[ufukty]

Maybe there is a misunderstanding. This already is the feature request you suggested me to send to the feedback URL. It redirects here. Other hand, thanks for the suggestions.

Best,