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

Assigning a Task without Assigning the Project #2384

New Issue
Open
opened 2026-03-22 14:05:18 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-22 14:05:18 -05:00
Owner
Copy Link

Originally created by @ccalby on GitHub (Oct 12, 2025).

Description

Hi all,

A feature suggestion from me:

Problem

To assign someone a task today, I must add them to the whole project, which exposes unrelated tasks and data.

Proposal

Enable task-level sharing/assignment so a user can be invited to one task only. You could do this on a "Share Task" type approach (similar to say, Google Drive) with roles such as:

  • Viewer: read task details.
  • Contributor: comment, upload attachments, update checklists/subtasks, change status.
  • Manager: edit core fields (title, description, labels, due dates, assignees) — for this task only.

Or just share with who the task is "assigned to".

Use cases

  • One-off collaboration with another team (e.g., legal review).
  • Privacy-sensitive projects needing least-privilege access.

Which alternatives did you consider using instead?

No response

Originally created by @ccalby on GitHub (Oct 12, 2025). ### Description Hi all, A feature suggestion from me: ### Problem To assign someone a task today, I must add them to the whole project, which exposes unrelated tasks and data. ### Proposal Enable task-level sharing/assignment so a user can be invited to one task only. You could do this on a "Share Task" type approach (similar to say, Google Drive) with roles such as: - Viewer: read task details. - Contributor: comment, upload attachments, update checklists/subtasks, change status. - Manager: edit core fields (title, description, labels, due dates, assignees) — for this task only. Or just share with who the task is "assigned to". ### Use cases - One-off collaboration with another team (e.g., legal review). - Privacy-sensitive projects needing least-privilege access. ### Which alternatives did you consider using instead? _No response_
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#2384
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?