Team Permission Table Bug

[AaronS8]

Gitea Version

1.16.0 && 1.17.0+dev-32-gab7f70167

Git Version

2.33

Operating System

Windows 10

How are you running Gitea?

I'am running Gitea as a service

Database

PostgreSQL

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Description

Team Permmission Table bugs

Bugs

1. if I give a team admin rights I can't change it back to general access
2. if I give a team general access and give all read permission but one permission to write access, the team have readonly access
3. and team members won't be able to assigned a project even if they have write access on code, issue which means they aren't recoginzed as collabrators

Tested Databases

• MSSQLServer
• MySql
• Sqlite

Links

https://gitea.com/org/BugTester/teams/collabrotors/edit

Screenshots

[Gusted]

I was able to reproduce the first and third bug. The first bug was a regression and is fixed by #18496, the third bug is another issue which was is currently the behavior(so it should be a new issue as enhancement). The second bug is too vague to understand/reproduce.

[lunny]

The first bug is when check admin access and then check general access, the access table will not be shown again.

[AaronS8]

@lunny setting the general access and admin is fixed but the team mebers can't be assigned an issue even if they have write permmision in the code and read or write on the issue and one read permssion (any unit) .
but if there is no read only permission only write and no access the problems doesn't exist, They can be assigned

[zeripath]

1. if I give a team admin rights I can't change it back to general access I think this is fixed by Use "read" value for General Access #18496
2. if I give a team general access and give all read permission but one permission to write access, the team have readonly access
3. team members won't be able to assigned a project even if they have write access on code, issue which means they aren't recoginzed as collabrators

[zeripath]

As @Gusted said above we're a little confused by number 2 here. Would it be possible for you to create an org with teams on try.gitea.io that replicates the issue. Use temporary users that you can share the passwords of here.

[AaronS8]

Sorry I couldn't create temporary users in try.gitea.io since I have slow internet, but I think number 2 is fixed after I upgraded my gitea to v1.17.0+dev-75-g7f2530e00.