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 #1440] Putting Projects On Hold #6394

New Issue
Open
opened 2026-04-20 16:59:30 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-20 16:59:30 -05:00
Owner
Copy Link

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

Description

As I am cleaning up our task views, I realized quite a few projects fall into one of two categories:

  • paused projects that are currently on hold because of other commitments
  • projects where I am inside as a (re)viewer or maybe product owner, but not actually to work on the tasks

Tasks from both of these should not show up in my tasks overview - and they could basically get the same treatment: An option to put a project "on hold" / "inactive" for me, which excludes all its tasks from my views and maybe greys it out a bit in the sidebar.
Basically an archiving light feature, cause I still want to be able to add tasks and see them but not have them show up in the overviews.

Which alternatives did you consider using instead?

archiving and unarchiving which is a bit cumbersome

Originally created by @xeruf on GitHub (Sep 8, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1440 ### Description As I am cleaning up our task views, I realized quite a few projects fall into one of two categories: - paused projects that are currently on hold because of other commitments - projects where I am inside as a (re)viewer or maybe product owner, but not actually to work on the tasks Tasks from both of these should not show up in my tasks overview - and they could basically get the same treatment: An option to put a project "on hold" / "inactive" for me, which excludes all its tasks from my views and maybe greys it out a bit in the sidebar. Basically an archiving light feature, cause I still want to be able to add tasks and see them but not have them show up in the overviews. ### Which alternatives did you consider using instead? archiving and unarchiving which is a bit cumbersome
GiteaMirror added the concern/uxarea/projectsarea/views labels 2026-04-20 16:59:30 -05:00
GiteaMirror commented 2026-04-20 16:59:31 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 8, 2025):

What about adding a saved filter which excludes the projects which you don't want to see?

<!-- gh-comment-id:3267954375 --> @kolaente commented on GitHub (Sep 8, 2025): What about adding a saved filter which excludes the projects which you don't want to see?
GiteaMirror commented 2026-04-20 16:59:32 -05:00
Author
Owner
Copy Link

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

then I need to do that to all filters which is a bit annoying if I have multiple filters

<!-- gh-comment-id:3275441035 --> @xeruf commented on GitHub (Sep 10, 2025): then I need to do that to all filters which is a bit annoying if I have multiple filters
GiteaMirror commented 2026-04-20 16:59:33 -05:00
Author
Owner
Copy Link

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

a bit like muted streams / topics in slack / zulip

<!-- gh-comment-id:3275447431 --> @xeruf commented on GitHub (Sep 10, 2025): a bit like muted streams / topics in slack / zulip
GiteaMirror commented 2026-04-20 16:59:34 -05:00
Author
Owner
Copy Link

@breeegz commented on GitHub (Oct 23, 2025):

I was recently cleaning up old tasks that I never finished and I wasn't going to do anymore (for whatever reason), and I wasn't ready to completely nuke them. There was some history in the comments that I wanted to keep or whatever other reason that deleting didn't seem like a good option.

I ended clicking "Done" even though I was thinking that I needed a cancelled, or a closed, or some other term that is meaningful to the user that isn't "Done". The "Done Bucket" seems to have special handling.

As I was thinking about it, if tags were enhance and a little more powerful, like a tag defining the state, "Done" could be a state-tag, and so could "Canceled", "OBE", "Unfunded", "On-Hold", "Inactive", etc.

Kanban buckets could be assigned "state-tags" and act as a filter.

--After typing all of this, I realized that you were talking about the Project level, and not the task level. I'll leave my paragraphs because maybe it is worth something even at the Project level.

<!-- gh-comment-id:3435204977 --> @breeegz commented on GitHub (Oct 23, 2025): I was recently cleaning up old tasks that I never finished and I wasn't going to do anymore (for whatever reason), and I wasn't ready to completely nuke them. There was some history in the comments that I wanted to keep or whatever other reason that deleting didn't seem like a good option. I ended clicking "Done" even though I was thinking that I needed a cancelled, or a closed, or some other term that is meaningful to the user that isn't "Done". The "Done Bucket" seems to have special handling. As I was thinking about it, if tags were enhance and a little more powerful, like a tag defining the state, "Done" could be a state-tag, and so could "Canceled", "OBE", "Unfunded", "On-Hold", "Inactive", etc. Kanban buckets could be assigned "state-tags" and act as a filter. --After typing all of this, I realized that you were talking about the Project level, and not the task level. I'll leave my paragraphs because maybe it is worth something even at the Project level.
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/views concern/ux
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#6394
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?