Why is there no triage in base permissions

[maliberty]

Select Topic Area

Question

Select Feature Area

• Issues
• Projects

Body

In the settings/member_privileges there is a drop down for 'Base permissions' that has read and write but not triage:

I would like to give the base as triage. As a workaround I created a team and gave it triage permission and invited everyone into it. It would be simpler if I could just set it as the base.

Guidelines

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

[queenofcorgis]

Thanks for posting in the GitHub Community, @maliberty !

We're happy you're here. You are more likely to get a useful response if you are posting your question in the applicable category, the Issues category is solely related to conversations around the GitHub products Issues and Projects. I've gone ahead and moved it for you. Good luck!

[maliberty]

@queenofcorgis Thanks. I thought my question related to Projects but I guess not.

[Alex-ley-scrub]

@queenofcorgis where is this being tracked now? This issue is still present.
Or is it still this url it was just reclassified to the repositories topic?

[queenofcorgis]

@Alex-ley-scrub this is still the correct URL - I just added the proper label to categorize this as feedback so the team can review. Feel free to add any more details if you'd like to help our team understand how this can be improved.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[maliberty]

This remains relevant to me and unsolved.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[maliberty]

Again "This remains relevant to me and unsolved."

[bocytko]

+1. This would be incredibly useful for any repository with a high number of contributors, such as internal frameworks or documentation sites. Without the Triage permission, the contributors cannot add labels, assign issues to themselves, etc. A workaround is to implement custom bots that react to comments.

There is no workaround for not being able to resolve comment threads on PRs that one is an author of.

[nfstein]

+1 My team is encountering this as well. We would like to default users in an org to the triage role.

[kaisensan]

Why is this closed? It's still a relevant issue and I was hoping GitHub could provide such functionality, it'd be especially helpful for GitHub Enterprise.

[maliberty]

I wish I knew - it appears they close things after a while regardless of relevance.