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

[GH-ISSUE #285] Adding 'labels != <anything>' filter filters out all issues without a label set #6044

New Issue
Closed
opened 2026-04-20 16:35:00 -05:00 by GiteaMirror · 12 comments
GiteaMirror commented 2026-04-20 16:35:00 -05:00
Owner
Copy Link

Originally created by @bayger on GitHub (Jul 9, 2024).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/285

Description

If you try to add any filter to NOT show issues with a particular label it also filters out all issues that have no label set. Expected behavior would be to show also issues without any label set and only filter out issues with specified label in the filter.

How to reproduce on the demo site:

  • go to Inbox project
  • edit List view and add '&& labels != Personal' to the filter
  • all issues without label set will disappear

Vikunja Version

0.24

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Originally created by @bayger on GitHub (Jul 9, 2024). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/285 ### Description If you try to add any filter to NOT show issues with a particular label it also filters out all issues that have no label set. Expected behavior would be to show also issues without any label set and only filter out issues with specified label in the filter. How to reproduce on the demo site: - go to Inbox project - edit List view and add '&& labels != Personal' to the filter - all issues without label set will disappear ### Vikunja Version 0.24 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
GiteaMirror added the enhancement label 2026-04-20 16:35:00 -05:00
GiteaMirror commented 2026-04-20 16:35:02 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 10, 2024):

Does it work if you check the checkbox below the filter input which says 'include tasks which don't have a value set'?

<!-- gh-comment-id:2219988993 --> @kolaente commented on GitHub (Jul 10, 2024): Does it work if you check the checkbox below the filter input which says 'include tasks which don't have a value set'?
GiteaMirror commented 2026-04-20 16:35:03 -05:00
Author
Owner
Copy Link

@bayger commented on GitHub (Jul 10, 2024):

Does it work if you check the checkbox below the filter input which says 'include tasks which don't have a value set'?

I don't have such checkbox available. Is it something new? My version is 0.24.0.
image

<!-- gh-comment-id:2220367030 --> @bayger commented on GitHub (Jul 10, 2024): > Does it work if you check the checkbox below the filter input which says 'include tasks which don't have a value set'? I don't have such checkbox available. Is it something new? My version is 0.24.0. ![image](https://github.com/go-vikunja/vikunja/assets/2379135/f5c9cd4d-0982-4ae7-b487-4cb33ae07023)
GiteaMirror commented 2026-04-20 16:35:03 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 10, 2024):

Ah, I thought you were using the filter in the view. I think to solve this properly, we'll need to implement null filtering as requested here and get rid of the checkbox: https://community.vikunja.io/t/filtering-search-for-null/2572/3

<!-- gh-comment-id:2220395132 --> @kolaente commented on GitHub (Jul 10, 2024): Ah, I thought you were using the filter in the view. I think to solve this properly, we'll need to implement null filtering as requested here and get rid of the checkbox: https://community.vikunja.io/t/filtering-search-for-null/2572/3
GiteaMirror commented 2026-04-20 16:35:04 -05:00
Author
Owner
Copy Link

@bayger commented on GitHub (Jul 10, 2024):

Now I wonder if we could simply return TRUE for the inequality operator applied to an empty/null entity? Or would it screw up something elsewhere? Not sure about the expected behavior there though.

<!-- gh-comment-id:2220505660 --> @bayger commented on GitHub (Jul 10, 2024): Now I wonder if we could simply return TRUE for the inequality operator applied to an empty/null entity? Or would it screw up something elsewhere? Not sure about the expected behavior there though.
GiteaMirror commented 2026-04-20 16:35:04 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 10, 2024):

It's not as simple as that, because the query is translated to a sql query under the hood.

<!-- gh-comment-id:2220935034 --> @kolaente commented on GitHub (Jul 10, 2024): It's not as simple as that, because the query is translated to a sql query under the hood.
GiteaMirror commented 2026-04-20 16:35:04 -05:00
Author
Owner
Copy Link

@horusofoz commented on GitHub (Jan 1, 2025):

Would the proposed null filter also allow for filtering tasks where startDate is not set?

<!-- gh-comment-id:2566819988 --> @horusofoz commented on GitHub (Jan 1, 2025): Would the proposed null filter also allow for filtering tasks where startDate is not set?
GiteaMirror commented 2026-04-20 16:35:05 -05:00
Author
Owner
Copy Link

@nosbig commented on GitHub (Jan 10, 2025):

I would love to have null filtering/searching as well, as I'd like to build a filter to find all tasks with no labels so that I can work a backlog queue and assign labels for any tasks missing my desired label structure.

<!-- gh-comment-id:2582171968 --> @nosbig commented on GitHub (Jan 10, 2025): I would love to have null filtering/searching as well, as I'd like to build a filter to find all tasks with no labels so that I can work a backlog queue and assign labels for any tasks missing my desired label structure.
GiteaMirror commented 2026-04-20 16:35:05 -05:00
Author
Owner
Copy Link

@0KayKay commented on GitHub (Mar 31, 2025):

I'd also love to use that null filter. All is fine when the tasks are filled out completely, but at some point I make a mistake when I create one and lose it. It would be very convenient to explicitly search for those tasks and filter out everything else.

<!-- gh-comment-id:2765470987 --> @0KayKay commented on GitHub (Mar 31, 2025): I'd also love to use that null filter. All is fine when the tasks are filled out completely, but at some point I make a mistake when I create one and lose it. It would be very convenient to explicitly search for those tasks and filter out everything else.
GiteaMirror commented 2026-04-20 16:35:05 -05:00
Author
Owner
Copy Link

@vovochka404 commented on GitHub (Apr 4, 2025):

@kolaente will u be interested in PR with such filter conditions implemented? And if so, do you have any thoughts on it? Or i can try to implement it and then we will discuss it in PR?

P.S. Thank you for your job :)

<!-- gh-comment-id:2778279607 --> @vovochka404 commented on GitHub (Apr 4, 2025): @kolaente will u be interested in PR with such filter conditions implemented? And if so, do you have any thoughts on it? Or i can try to implement it and then we will discuss it in PR? P.S. Thank you for your job :)
GiteaMirror commented 2026-04-20 16:35:06 -05:00
Author
Owner
Copy Link

@CoffeePerry commented on GitHub (Apr 4, 2025):

The following filter also does not work properly:

assignees != simoneperini

Even though it is flagged "include tasks which don't have a value set".
Tasks that do not have an assignee set do not appear.

<!-- gh-comment-id:2778363109 --> @CoffeePerry commented on GitHub (Apr 4, 2025): The following filter also does not work properly: ``` assignees != simoneperini ``` Even though it is flagged "_include tasks which don't have a value set_". Tasks that do not have an assignee set do not appear.
GiteaMirror commented 2026-04-20 16:35:06 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Apr 9, 2025):

@vovochka404 I'd happily take a PR implementing null as a keyword for filters!

The most straight-forward way to implement this would be by just translating the null to a null in the database. Related entities (like reminders or labels) would need a little more work, though.

<!-- gh-comment-id:2790386640 --> @kolaente commented on GitHub (Apr 9, 2025): @vovochka404 I'd happily take a PR implementing null as a keyword for filters! The most straight-forward way to implement this would be by just translating the null to a `null` in the database. Related entities (like reminders or labels) would need a little more work, though.
GiteaMirror commented 2026-04-20 16:35:06 -05:00
Author
Owner
Copy Link

@vovochka404 commented on GitHub (Apr 15, 2025):

Currently i'm having troubles with typesence, cause it doesn't support any checks against null/existence.

As i can see, you also skipped filterIncludeNulls flag when working with typesence. What are your thoughts about this inconsistency?

<!-- gh-comment-id:2804591329 --> @vovochka404 commented on GitHub (Apr 15, 2025): Currently i'm having troubles with typesence, cause it doesn't support any checks against null/existence. As i can see, you also skipped `filterIncludeNulls` flag when working with typesence. What are your thoughts about this inconsistency?
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 enhancement
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#6044
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?