List moved into namespace does not inherit permissions #1992

Closed
opened 2022-10-14 10:50:23 +00:00 by xeruf · 1 comment

Version information:

Frontend Version: 19
API Version: 19
Browser and OS Version: Firefox on Arch

Steps to reproduce:

  1. Create a namespace and share it to another user ("Bob")
  2. Log in as Bob, create a private list and move it to the namespace
  3. Log in as original user

Expected behavior:

Lists inherit permissions from namepace

Actual behavior:

No ability to share the list with users and teams, despite admin permission on the namespace.

This holds true even if you add both to a team which has admin permission on the namespace.

Checklist:

  • I have provided all required information
  • I am using the latest release or the latest unstable build
  • I was able to reproduce the bug on try
<!-- Please fill out this issue template to report a bug. If you want to propose a new feature, please open a discussion thread in the forum: https://community.vikunja.io --> **Version information:** Frontend Version: 19 API Version: 19 Browser and OS Version: Firefox on Arch **Steps to reproduce:** 1. Create a namespace and share it to another user ("Bob") 2. Log in as Bob, create a private list and move it to the namespace 3. Log in as original user **Expected behavior:** Lists inherit permissions from namepace **Actual behavior:** No ability to share the list with users and teams, despite admin permission on the namespace. This holds true even if you add both to a team which has admin permission on the namespace. **Checklist:** * [x] I have provided all required information * [x] I am using the latest release or the latest unstable build * [x] I was able to reproduce the bug on [try](https://try.vikunja.io)
konrad added the
kind/bug
label 2022-10-18 08:37:07 +00:00
Owner

Resolved by 8a5b1ab3e3 and 9fc08a0790. Please check with the next unstable build (in ~30 min) if the problem really went away.

Resolved by 8a5b1ab3e3c22fa2c6922b0c14272f5320d8cf16 and https://kolaente.dev/vikunja/api/commit/9fc08a0790fcd8ceaaebbfed0232cdc95e91924e. Please check with the next unstable build (in ~30 min) if the problem really went away.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/vikunja#1992
No description provided.