I’m on the latest unstable build. Moving tasks between kanban buckets seems to need Admin permissions now.
I’ve found several issues while trying to set up things correctly. We use teams to give a lot of people access to projects.
Previously, the project shared with Read/Write permissions to the team. Setting it to Admin fixes the moving between buckets issue, so far so good. I can see that you need to give the team admin permissions (although I’m not sure why moving between buckets would require admin permissions, seems a bit random).
Anyway, having the team as admin for the project now apparently also means that every member of the team can do things like delete the project making the permissions to move tasks between buckets and to delete project equal which doesn’t make sense. Even the team internal member/admin settings don’t seem to have any effect on this.
Maybe I’m misinterpreting this, but the current setup seems a little broken.
These kind of permission configurations who can delete a board or move between tasks and so on is what I mean in this feature request:
Got the same error, but I’m still on an older version (Vikunja api version v0.23.0+551-324df991ce). Is it advisable to update to the current nightly?
Here’s what my log says:
2024-06-01T22:00:16.26703967+02:00: NOTICE ▶ routes/1 c814 Tried to update while not having the rights for it (User: &{2 Thomas Nesges nesges thomas@pnpde.social Active 0 false false false false 0 0 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC <nil> 0 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC <nil>})
2024-06-02T17:28:48.556716823+02:00: NOTICE ▶ routes/1 1bf Tried to update while not having the rights for it (User: &{2 Thomas Nesges nesges thomas@pnpde.social Active 0 false false false false 0 0 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC <nil> 0 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC <nil>})
Thank you!