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

[GH-ISSUE #1388] Assignee Roles #6378

New Issue
Open
opened 2026-04-20 16:58:13 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 16:58:13 -05:00
Owner
Copy Link

Originally created by @xeruf on GitHub (Sep 2, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1388

Description

For some settings, it would be great to track a responsible person and the involved people, rather than just generic assignees.
Visually on the card / list view they should then be separated - responsible person first, other involved people grouped.

More generically, assignees could be assigned roles (lead, protocol, tooling, research, ...)

Which alternatives did you consider using instead?

Either tracking all involved people or only the responsible person

Originally created by @xeruf on GitHub (Sep 2, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1388 ### Description For some settings, it would be great to track a responsible person and the involved people, rather than just generic assignees. Visually on the card / list view they should then be separated - responsible person first, other involved people grouped. More generically, assignees could be assigned roles (lead, protocol, tooling, research, ...) ### Which alternatives did you consider using instead? Either tracking all involved people or only the responsible person
GiteaMirror added the area/task-metadataarea/permissions labels 2026-04-20 16:58:13 -05:00
GiteaMirror commented 2026-04-20 16:58:15 -05:00
Author
Owner
Copy Link

@xeruf commented on GitHub (Sep 2, 2025):

One step further would be bucket responsibilities and tasks moving across buckets like the classic Design->Dev->Testing->QA processes and being reassigned in the process, still deliberating how that could be handled well

<!-- gh-comment-id:3245714742 --> @xeruf commented on GitHub (Sep 2, 2025): One step further would be bucket responsibilities and tasks moving across buckets like the classic Design->Dev->Testing->QA processes and being reassigned in the process, still deliberating how that could be handled well
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 area/task-metadata
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#6378
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?