Filters are very unstable

[bramvdzee]

Description

There's a few things I've noticed with filters, both on the API and in the UI.

1. Chaining more than one filter completely breaks the filter. At least when using due dates. This is true in the API, direct filters and saved filters.
2. The cursor in the saved filters textbox often misaligns when typing. I find that this most often happens when it's trying to compensate for certain words (due_date being replaced with dueDate).
3. Saved Filters are assigned negative identifiers
4. Saved Filters are not queryable through the API (maybe because the ID is negative).

Are filters in active development right now? At the moment, it's not usable at all.

Vikunja Version

0.24.5

Browser and version

Safari MacOS & iOS

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

[kolaente]

Chaining more than one filter completely breaks the filter. At least when using due dates. This is true in the API, direct filters and saved filters.

Can you provide the exact filter queries which don't work? And how you're executing them?

The cursor in the saved filters textbox often misaligns when typing. I find that this most often happens when it's trying to compensate for certain words (due_date being replaced with dueDate).

That's definitely a bug.

Saved Filters are assigned negative identifiers

This is by design.

Saved Filters are not queryable through the API (maybe because the ID is negative).

They are queriable through the API, otherwise the Frontend wouldn't be able to show tasks from filters. How are you querying them?

[bramvdzee]

This the filter I'm trying to use in the UI for unfinished tasks, with a due date of the coming minute.
This is the API endpoint I'm trying to use: /api/v1/tasks/all?filter=done=false&&due_date>=now (also tried URL encoded).

Scratch that part about the Saved Filters. I saw that I didn't grant permission on my API key. Though I would've expected a different message than this:
{ "message": "missing, malformed, expired or otherwise invalid token provided" }

Edit: the API key permission message is more clear than I thought. It's getting late lol

[kolaente]

Did you get an error message when passing the filter? Or does it just not contain the tasks you were expecting?

[bramvdzee]

There’s no errors. It displays all tasks witout a due date with those filters, but I noticed that sometimes when I do +2h it does include the ones with a due date. Perhaps it’s a timezone issue?

[kolaente]

Did you configure your time zone?

[bramvdzee]

I did, it’s on Europe/Amsterdam. Both the docker container and the profile.

[kolaente]

Does it change if you use the next two minutes? This might be related to the one minute window.

[0KayKay]

I can confirm that this also happens if you do the same for days (f.e. "now+2d").

It seems like all items are included where the property is not set. I've encountered something similar with priority, where unset priorities are included when you do something like "priority > 2". I found a workaround for that using "priority in 3,4,5" but that's a bit complicated and definitely not working as intended.

[kolaente]

It seems like all items are included where the property is not set.

There is a checkbox below the filter to include or exclude tasks which do not have the property set, does that work for you?

[0KayKay]

Oh. Thank you, that directly solved my problem.

My setup was a saved filter with a couple of views to extend the filter logic. So I created the initial filter and didn't notice that the option was there. For the views with which I interacted the most, that option didn't exist.

Now I'm wondering if other people also fail to notice the existence of that option and then think that some functionality is broken. Because my expected default behaviour would have been that unset properties are filtered out. Maybe that lack of attention and the mismatch of default behaviour and expectations leads to unnecessary confusion. Just some food for thought.

Anyway, I greatly appreaciate the swift response.