-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Team Members Assignment on Issues #18555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I think the team members should be listed even if they have a readonly access on issue, but they should be able to be assigned on issues since they have access on code. |
It would be great after the team is given a readonly permission on all areas but write permmission on the code unit, they should be list on assign users filter list. |
I guess the problem is that we really need the assigned user to be able to close the issue/PR or merge the PR otherwise they're not really in control of that issue and someone else will need to do that for them. If that could be resolved, or is perhaps not relevant then I actually think any collaborator or team member with issue/pull request read access should be assignable for an issue/pull request respectively. Either that or we create another pair of permissions assignable to Issues, assignable to pull requests. |
I think collabrorator should be abel to close and open issues, the readonly permission
|
Should be resolved by #18680 |
Feature Description
I think it would be great if Gitea Enables Team members assigned on issues even if they have readonly permmission on issues,
I thought that was a bug but as @Gusted suggested on #18483 , I think it would be a good enhancement on gitea's team permssion area
Screenshots
No response
The text was updated successfully, but these errors were encountered: