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

[GH-ISSUE #32] Let user edit only 1 card in the list #5856

New Issue
Open
opened 2026-04-20 16:14:43 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-20 16:14:43 -05:00
Owner
Copy Link

Originally created by @tio-trom on GitHub (Jun 21, 2022).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/32

I would expect that if I assign a card to a user, the user can automatically edit that card/task. But it seems not to be the case. So is there a way to only share a card/task with a user and give the user edit permission?

Originally created by @tio-trom on GitHub (Jun 21, 2022). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/32 I would expect that if I assign a card to a user, the user can automatically edit that card/task. But it seems not to be the case. So is there a way to only share a card/task with a user and give the user edit permission?
GiteaMirror added the area/permissions label 2026-04-20 16:14:43 -05:00
GiteaMirror commented 2026-04-20 16:14:46 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jun 29, 2022):

Users will only be able to edit a task if you give them at least write access to the list. Assignees are a different concept, they only show who should be responsible for a task.

<!-- gh-comment-id:1171409688 --> @kolaente commented on GitHub (Jun 29, 2022): Users will only be able to edit a task if you give them at least write access to the list. Assignees are a different concept, they only show who should be responsible for a task.
GiteaMirror commented 2026-04-20 16:14:47 -05:00
Author
Owner
Copy Link

@tio-trom commented on GitHub (Jun 29, 2022):

But if you give them write access to the list it means they can edit any card/task in the list?

<!-- gh-comment-id:1171409691 --> @tio-trom commented on GitHub (Jun 29, 2022): But if you give them write access to the list it means they can edit any card/task in the list?
GiteaMirror commented 2026-04-20 16:14:48 -05:00
Author
Owner
Copy Link

@dpschen commented on GitHub (Jun 29, 2022):

If I get it correctly: the problem might come from the fact that you can assign a user to a task that doesn’t have write access to the list. Maybe that is something that should change? 🤔

<!-- gh-comment-id:1171409696 --> @dpschen commented on GitHub (Jun 29, 2022): If I get it correctly: the problem might come from the fact that you can assign a user to a task that doesn’t have write access to the list. Maybe that is something that should change? 🤔
GiteaMirror commented 2026-04-20 16:14:49 -05:00
Author
Owner
Copy Link

@tio-trom commented on GitHub (Jun 29, 2022):

Yeah I would like to be able to give access to a task, and to a task only. Not to the entire list. This can be very helpful. The user can have read access to the list, but only write access to a task that he/she is assigned to.

<!-- gh-comment-id:1171409700 --> @tio-trom commented on GitHub (Jun 29, 2022): Yeah I would like to be able to give access to a task, and to a task only. Not to the entire list. This can be very helpful. The user can have read access to the list, but only write access to a task that he/she is assigned to.
GiteaMirror commented 2026-04-20 16:14:50 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jun 30, 2022):

But if you give them write access to the list it means they can edit any card/task in the list?

Yes.

I think this issue could be turned into a feature so that it behaves as you expected but it should be an option in the list's settings.

<!-- gh-comment-id:1171409706 --> @kolaente commented on GitHub (Jun 30, 2022): > But if you give them write access to the list it means they can edit any card/task in the list? Yes. I think this issue could be turned into a feature so that it behaves as you expected but it should be an option in the list's settings.
GiteaMirror commented 2026-04-20 16:14:51 -05:00
Author
Owner
Copy Link

@tio-trom commented on GitHub (Jun 30, 2022):

Could be very useful if it can be implemented. I wanted some help with a particular task from someone I do not know that well, but I was not comfortable to give him full write access to the entire list (tens of tasks). In any case, hopefully this can be added. Thanks!

<!-- gh-comment-id:1171486114 --> @tio-trom commented on GitHub (Jun 30, 2022): Could be very useful if it can be implemented. I wanted some help with a particular task from someone I do not know that well, but I was not comfortable to give him full write access to the entire list (tens of tasks). In any case, hopefully this can be added. Thanks!
GiteaMirror commented 2026-04-20 16:14:51 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 2, 2022):

I've added an item to the backlog for this.

<!-- gh-comment-id:1172891911 --> @kolaente commented on GitHub (Jul 2, 2022): I've added an item to the backlog for this.
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 area/permissions
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#5856
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?