Skip to content
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

Team Members Assignment on Issues #18555

Closed
AaronS8 opened this issue Feb 2, 2022 · 7 comments
Closed

Team Members Assignment on Issues #18555

AaronS8 opened this issue Feb 2, 2022 · 7 comments
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@AaronS8
Copy link

AaronS8 commented Feb 2, 2022

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

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Feb 3, 2022
@AaronS8
Copy link
Author

AaronS8 commented Feb 3, 2022

ReadOnly
readonly1

@AaronS8
Copy link
Author

AaronS8 commented Feb 3, 2022

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.

@AaronS8
Copy link
Author

AaronS8 commented Feb 3, 2022

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.

@zeripath
Copy link
Contributor

zeripath commented Feb 3, 2022

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.

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.

@AaronS8
Copy link
Author

AaronS8 commented Feb 3, 2022

I think collabrorator should be abel to close and open issues, the readonly permission

  1. should limit them from editing comments other than theirs and making changes on the left side of the menu like Assigning, labeling
  2. should limit them from editing on the projects created by other users.

@AaronS8
Copy link
Author

AaronS8 commented Feb 3, 2022

@zeripath found a bug on 1.16.0 && 1.17 and opened it on #18572, it could be realted to this issue.

@lunny
Copy link
Member

lunny commented Mar 1, 2022

Should be resolved by #18680

@lunny lunny closed this as completed Mar 1, 2022
@go-gitea go-gitea locked and limited conversation to collaborators Apr 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

3 participants