Team Members Assignment on Issues #8468

New Issue

GiteaMirror · 2025-11-02T08:07:21-06:00

GiteaMirror commented

2025-11-02 08:07:21 -06:00

Originally created by @AaronS8 on GitHub (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

Originally created by @AaronS8 on GitHub (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_

GiteaMirror added the type/proposal label 2025-11-02 08:07:21 -06:00

GiteaMirror closed this issue

2025-11-02 08:07:21 -06:00

GiteaMirror commented

2025-11-02 08:07:22 -06:00

@AaronS8 commented on GitHub (Feb 3, 2022):

@AaronS8 commented on GitHub (Feb 3, 2022): ![ReadOnly](https://user-images.githubusercontent.com/98172519/152286012-fcd24773-d514-491e-8b26-61a645af53c9.jpg) ![readonly1](https://user-images.githubusercontent.com/98172519/152286016-95216b8e-a521-4ca8-b970-c2182d7a2a07.jpg)

GiteaMirror commented

2025-11-02 08:07:22 -06:00

@AaronS8 commented on GitHub (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 commented on GitHub (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.

GiteaMirror commented

2025-11-02 08:07:23 -06:00

@AaronS8 commented on GitHub (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.

@AaronS8 commented on GitHub (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.

GiteaMirror commented

2025-11-02 08:07:23 -06:00

@zeripath commented on GitHub (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.

@zeripath commented on GitHub (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.

GiteaMirror commented

2025-11-02 08:07:24 -06:00

@AaronS8 commented on GitHub (Feb 3, 2022):

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

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

@AaronS8 commented on GitHub (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.

GiteaMirror commented

2025-11-02 08:07:24 -06:00

@AaronS8 commented on GitHub (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.

@AaronS8 commented on GitHub (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.

GiteaMirror commented

2025-11-02 08:07:25 -06:00

@lunny commented on GitHub (Mar 1, 2022):

Should be resolved by #18680

@lunny commented on GitHub (Mar 1, 2022): Should be resolved by #18680

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#8468