github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-09 05:18:10 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

Project created in shared project not available to shared project admin #2222

New Issue
Closed
opened 2026-03-22 13:58:08 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-03-22 13:58:08 -05:00
Owner
Copy Link

Originally created by @AliveDevil on GitHub (May 4, 2025).

Description

With the current v0.24.6, when sharing a project with another user (as admin), that user can see and access all projects.
But, once this user creates a project in that shared project, the originally sharing user of that project doesn't have access to that project, and needs resharing.

Steps performed:

  • User A creates project X
  • User A shared project X with user B, as Admin
  • User A creates project Y with X as parent
    User B can access project Y, with full admin permissions
  • User B creates project Z with X as parent
    User A cannot access project Z, despite having created the parent project
  • User B shares project Z with A, and A can now access project Z

Vikunja Version

v0.24.6

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @AliveDevil on GitHub (May 4, 2025). ### Description With the current v0.24.6, when sharing a project with another user (as admin), that user can see and access all projects. But, once this user creates a project in that shared project, the originally sharing user of that project doesn't have access to that project, and needs resharing. Steps performed: - User A creates project X - User A shared project X with user B, as Admin - User A creates project Y with X as parent User B can access project Y, with full admin permissions - User B creates project Z with X as parent User A cannot access project Z, despite having created the parent project - User B shares project Z with A, and A can now access project Z ### Vikunja Version v0.24.6 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-03-22 13:58:08 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jun 13, 2025):

Can you reproduce this with the latest unstable build?

@kolaente commented on GitHub (Jun 13, 2025): Can you reproduce this with the latest unstable build?
GiteaMirror commented 2026-03-22 13:58:09 -05:00
Author
Owner
Copy Link

@AliveDevil commented on GitHub (Jun 13, 2025):

I've just checked by copying my current db over to unstable, and can indeed confirm that there's no permission error when opening the previously not working project.

@AliveDevil commented on GitHub (Jun 13, 2025): I've just checked by copying my current db over to unstable, and can indeed confirm that there's no permission error when opening the previously not working project.
GiteaMirror commented 2026-03-22 13:58:09 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jun 13, 2025):

Then it's already fixed and just not yet released.

@kolaente commented on GitHub (Jun 13, 2025): Then it's already fixed and just not yet released.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2222
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?