Open timaw7 opened 1 week ago
As you are using a old version, maybe this is caused by an old bug, and has been fixed for newly added admin teams. IIRC, for existing admin teams, there's only one way to fix it: change to general access, set all permission to write and save. Then change to admin again and save.
I think #24012 has fixed this issue. Why it happened again. I forgot the details of it. Let me have a look....
Description
This was present on 1.21.11 as well.
A user defined as full administrator only for an organization is unable to shift project issues between columns. They are essentially at a read-only permission state. The permissions are defined as the following.
I would expect that this would give them full access on project boards for that organization. I was able to mitigate this by adding a new team with project write access in addition to the system admin for that org.
Gitea Version
1.22.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.43.5
Operating System
Rocky 9.4
How are you running Gitea?
Self hosted from binary with systemd.
Database
MSSQL