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

Filtering on assignee does not work as expected #2252

New Issue
Closed
opened 2026-03-22 13:59:06 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-03-22 13:59:06 -05:00
Owner
Copy Link

Originally created by @RosanneZe on GitHub (Jul 8, 2025).

Description

Bug
If I make a filter with assignees in my_username, then I get all tasks assigned to me, but also tasks without any assingees. I do not have the 'Include Tasks which don't have a value set' checkbox checked.

Expected behaviour
When I make a filter with assignees in my_username, I expect to see only my tasks, not unassigned tasks.

Reproducability on demo site
I was able to reproduce this on 22-6-2025 on the demo, but when I tried today the demo would not accept the username in the filter because it contained a -.

Vikunja Version

nightly of 4th July

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @RosanneZe on GitHub (Jul 8, 2025). ### Description **Bug** If I make a filter with `assignees in my_username`, then I get all tasks assigned to me, but also tasks without any assingees. I do not have the 'Include Tasks which don't have a value set' checkbox checked. **Expected behaviour** When I make a filter with `assignees in my_username`, I expect to see only my tasks, not unassigned tasks. **Reproducability on demo site** I was able to reproduce this on 22-6-2025 on the demo, but when I tried today the demo would not accept the username in the filter because it contained a `-`. ### Vikunja Version nightly of 4th July ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-03-22 13:59:07 -05:00
Author
Owner
Copy Link

@FlorianBreitenlacher commented on GitHub (Jul 21, 2025):

Hi, I use assignees in my_username && done = false to get my open tasks.

I agree that = should behave the same way, but the example shows assignees in my_username1, my_username2.

@FlorianBreitenlacher commented on GitHub (Jul 21, 2025): Hi, I use `assignees in my_username && done = false` to get my open tasks. I agree that `=` should behave the same way, but the example shows `assignees in my_username1, my_username2`.
GiteaMirror commented 2026-03-22 13:59:08 -05:00
Author
Owner
Copy Link

@RosanneZe commented on GitHub (Jul 21, 2025):

@FlorianBreitenlacher Ah, thanks for sharing. I actually always use in, but apparently with all the issues I had with the demo and trying to remember everything I tried, I messed up in my post. I'll change it.

The problem is that when I use in, I don't get tasks that are assigned to other people, but I do get unassigned tasks, which I don't want.

@RosanneZe commented on GitHub (Jul 21, 2025): @FlorianBreitenlacher Ah, thanks for sharing. I actually always use `in`, but apparently with all the issues I had with the demo and trying to remember everything I tried, I messed up in my post. I'll change it. The problem is that when I use `in`, I don't get tasks that are assigned to other people, but I do get unassigned tasks, which I don't want.
GiteaMirror commented 2026-03-22 13:59:08 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Aug 3, 2025):

@RosanneZe did you enable the "Show tasks without a value set" checkbox?

@kolaente commented on GitHub (Aug 3, 2025): @RosanneZe did you enable the "Show tasks without a value set" checkbox?
GiteaMirror commented 2026-03-22 13:59:09 -05:00
Author
Owner
Copy Link

@RosanneZe commented on GitHub (Aug 4, 2025):

@kolaente I did not have that checkbox checked (I did mention that in my description under 'bug', but I can add under a different heading if it wasn't clear enough?)

@RosanneZe commented on GitHub (Aug 4, 2025): @kolaente I did not have that checkbox checked (I did mention that in my description under 'bug', but I can add under a different heading if it wasn't clear enough?)
GiteaMirror commented 2026-03-22 13:59:09 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Aug 6, 2025):

I'm unable to reproduce this. Are you using a saved filter or a filter in a project?

@kolaente commented on GitHub (Aug 6, 2025): I'm unable to reproduce this. Are you using a saved filter or a filter in a project?
GiteaMirror commented 2026-03-22 13:59:09 -05:00
Author
Owner
Copy Link

@RosanneZe commented on GitHub (Aug 11, 2025):

@kolaente I had the issue in a saved filter in:
Frontend version: v0.24.1-1732-gb1b3c204
API version: v0.24.1-1732-b1b3c204

I tried to reproduce it in the demo, and I couldn't anymore. So I played around a bit more, and it turned out to be a different bug, the saved filter just didn't update, no matter what I put in the filter. I removed the filter and remade it. Luckily I only had one extra custom view in it, so it wasn't too much hassle. But very weird issue...

@RosanneZe commented on GitHub (Aug 11, 2025): @kolaente I had the issue in a saved filter in: Frontend version: v0.24.1-1732-gb1b3c204 API version: v0.24.1-1732-b1b3c204 I tried to reproduce it in the demo, and I couldn't anymore. So I played around a bit more, and it turned out to be a different bug, the saved filter just didn't update, no matter what I put in the filter. I removed the filter and remade it. Luckily I only had one extra custom view in it, so it wasn't too much hassle. But very weird issue...
GiteaMirror commented 2026-03-22 13:59:10 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Aug 11, 2025):

I'd consider this solved then. Please ping if you think there are other problems.

@kolaente commented on GitHub (Aug 11, 2025): I'd consider this solved then. Please ping if you think there are other problems.
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#2252
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?