I try v1.0.0-rc1 atm, and when creating a filter with “labels in..”, the form field does not allow to add a blank after" in" and I can not filter by labels.
Other filters like “project =…” are ok.
Edit: I have updated from the current stable version with existing tasks, filters, labels etc.
A quick reply if anybody has the same problem or if somehow the error only occurs in my installation would be nice.
This will be fixed in Fix filter labels by Saxos-Simone · Pull Request #1333 · go-vikunja/vikunja · GitHub
Any plans when V1.0.0-r2 will be created?
When the remaining bugs are fixed 
You can already try out the fix in an unstable build.
Yeah, I tried but when I use the current unstable binary instead of the v1.0.0-rc1, it won’t even start.
So I was hoping for a rc2 that is at least runnable.
Meanwhile I will stay on 0.24.6 and check every once in a while if a new release is published.
What does it say in the logs?
Ok, now I had some time to read the logs. I had an error in the config that is no longer tolerated in the unstable build.
Unfortunately, I know can add the “labels in …” filter, but it is not applied and all task are shown.
Can you reproduce the same filter on the demo?
I#ve created a “finance in” and a “finance eq” filter and it has the same problem. All Task are shown
What’s the exact query you’ve used?
Oh, sorry, I thought you could look at the demo and see the filter directly.
Here are some screenshots.
Is this the same problem? Saved filter: Editing the complex expression is broken · Issue #1395 · go-vikunja/vikunja · GitHub
I don’t think so. I can create and save the filter now, but as my screenshot above shows, tasks that do not match the criteria are shown in the results.
If the filter “labels = finance” is used, I would assume that only tasks with the labels finance applied are shown.
I would like to support you and make more test to give you an more complete description of the problem, but I don’t have the time atm. I think some filter work, while others don’t, and it’s to complicated to try every possibility without digging deep and follow a complete testing protocol..
But I’m more than happy to give it a new try once you think the problems are solved.
It seems like you have the “show tasks without a value set” checkbox enabled. Does it work if you uncheck that?
Oh dear, that was stupid of me. When the option is disabled, it seems to work as I expect it to, as far as I can tell. My previous filters all seem to work again.
Maybe it’s just me, but I don’t find the option very intuitive. I would prefer it if the default setting were changed and it were initially deselected.
I apologize for the confusion I have caused.
The checkbox will disappear at some point in the future in favour of allowing to filter by empty values directly in queries (like labels = null).
