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

Current Tasks View should by default be filtered to only my tasks #592

New Issue
Closed
opened 2025-11-01 20:59:55 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-01 20:59:55 -05:00
Owner
Copy Link

Originally created by @NeptunedGmbH on GitHub (Sep 4, 2025).

Description

I'm currently exploring Vikunja as an alternative to Trello in our company. There are a lot of things I like about it, especially the simplicity and speed of operation. I'm working in a company of non-technical people and so I need to find a really easy to use Project/Task-Manager with better permission management than Trello.
Vikunja is currently the best alternative I've found but I recently realized that the "Current Tasks" View always shows all Tasks. We're a company of 75 people. This View would be useless then... I think a usersetting to only show your own tasks in the "Current Tasks" View would be great. Additionally I'd like to be able to set a default in the config similar to the e-mail discoverability settings

Also it would be nice if this would also apply to the "Upcoming"-View

Which alternatives did you consider using instead?

No response

Originally created by @NeptunedGmbH on GitHub (Sep 4, 2025). ### Description I'm currently exploring Vikunja as an alternative to Trello in our company. There are a lot of things I like about it, especially the simplicity and speed of operation. I'm working in a company of non-technical people and so I need to find a really easy to use Project/Task-Manager with better permission management than Trello. Vikunja is currently the best alternative I've found but I recently realized that the "Current Tasks" View always shows all Tasks. We're a company of 75 people. This View would be useless then... I think a usersetting to only show your own tasks in the "Current Tasks" View would be great. Additionally I'd like to be able to set a default in the config similar to the e-mail discoverability settings Also it would be nice if this would also apply to the "Upcoming"-View ### Which alternatives did you consider using instead? _No response_
GiteaMirror commented 2025-11-01 20:59:56 -05:00
Author
Owner
Copy Link

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

But what you're describing is already the case?

It shows you only tasks which you have access to, not all tasks in the Vikunja instance. If you want to narrow it down more, you can create a saved filter and set that as the overview page in the user settings.

(There was a bug a long time ago which showed you all tasks from all users. If that's happening to you, you should upgrade your Vikunja instance, since that's a security risk)

@kolaente commented on GitHub (Sep 4, 2025): But what you're describing is already the case? It shows you only tasks which you have access to, not all tasks in the Vikunja instance. If you want to narrow it down more, you can create a saved filter and set that as the overview page in the user settings. (There was a bug a long time ago which showed you all tasks from all users. If that's happening to you, you should upgrade your Vikunja instance, since that's a security risk)
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#592
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?