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

[GH-ISSUE #2139] Add status metadata to projects #6555

New Issue
Open
opened 2026-04-20 17:09:06 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 17:09:06 -05:00
Owner
Copy Link

Originally created by @Jdogzz on GitHub (Jan 23, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2139

Description

As of now, projects in Vikunja can be given the following metadata:

  • Title (short form text)
  • Favorite (binary status)
  • Archive (binary status)
  • Description (long form text)

I would like to have the option to provide status metadata to projects beyond archive status. This may include the following:

Status keywords (similar to orgmode TODO states) selectable from a dropdown:

  • Not started
  • In progress
  • Stuck
  • Completed
  • Cancelled
  • Archived (project becomes hidden by default from views)

Completion statistics automatically calculated from tasks and subproject counts (similar to orgmode statistics cookies):

  • Count of tasks open vs. all tasks in project
  • Percentage of tasks open vs. all tasks in project
  • Count of subprojects open vs. all subprojects in project
  • Percentage of subprojects open vs. all subprojects in project

Having a visual indicator beside the project title (in the project view and the project tree view) corresponding to the status metadata would also be helpful to surface this metadata without clicks and tell at a glance the state of affairs. E.g. different symbols or colors to match status keywords, and a small ring or counter displaying completion statistics.

Which alternatives did you consider using instead?

As of now this would all have to be stuffed either in the project title text field or description.

Originally created by @Jdogzz on GitHub (Jan 23, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2139 ### Description As of now, projects in Vikunja can be given the following metadata: - Title (short form text) - Favorite (binary status) - Archive (binary status) - Description (long form text) I would like to have the option to provide status metadata to projects beyond archive status. This may include the following: Status keywords (similar to [orgmode TODO states](https://orgmode.org/manual/TODO-Basics.html)) selectable from a dropdown: - Not started - In progress - Stuck - Completed - Cancelled - Archived (project becomes hidden by default from views) Completion statistics automatically calculated from tasks and subproject counts (similar to [orgmode statistics cookies](https://orgmode.org/manual/Breaking-Down-Tasks.html)): - Count of tasks open vs. all tasks in project - Percentage of tasks open vs. all tasks in project - Count of subprojects open vs. all subprojects in project - Percentage of subprojects open vs. all subprojects in project Having a visual indicator beside the project title (in the project view and the project tree view) corresponding to the status metadata would also be helpful to surface this metadata without clicks and tell at a glance the state of affairs. E.g. different symbols or colors to match status keywords, and a small ring or counter displaying completion statistics. ### Which alternatives did you consider using instead? As of now this would all have to be stuffed either in the project title text field or description.
GiteaMirror added the area/task-metadataarea/projects labels 2026-04-20 17:09:06 -05:00
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/projects 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#6555
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?