Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

has_any_category:false not possible as a rule #8497

Closed
4 tasks done
shrippen opened this issue Feb 3, 2024 · 4 comments
Closed
4 tasks done

has_any_category:false not possible as a rule #8497

shrippen opened this issue Feb 3, 2024 · 4 comments
Labels
bug Verified and replicated bugs and issues. fixed Bugs that are fixed (in a coming release).

Comments

@shrippen
Copy link

shrippen commented Feb 3, 2024

Support guidelines

I've found a bug and checked that ...

Description

I want to create a rule that automatically assigns a specific tag to every transaction that has no category and is not a transfer.
I can search for has_any_category:true as mentioned in the docs and change the true to false. This will show every transaction without a category.
Then I click the button in the search page to convert my search to a rule. It shows the trigger "has (any) category" and inverts it. But this will not get results when I click on "show matching transactions"

Debug information

Debug information generated at 2024-02-03 12:09:14 for Firefly III version v6.1.7.

System information
ItemValue
Firefly IIIv6.1.7 / v2.0.12 / 22 (exp. 22)
PHP version8.3.2 / apache2handler / Linux
BCscale12
Error reportingDisplay: Off, reporting: ALL errors
Max upload67108864 (64 MB)
Database drivers*mysql*, pgsql, sqlite,
Docker build#933, base #79
Firefly III information
ItemValue
TimezoneEurope/Berlin + Europe/Berlin
App environmentlocal, debug: false
Layoutv1
Logginginfo, stack / (empty)
Cache driverfile
Default language and localede_DE + equal
Trusted proxies**
Login provider & user guardeloquent / web
Login headersN/A + N/A
Stateful domains
Last cron job2024-02-03 00:00:00 (12 hours ago)
Mailersmtp
User-specific information
ItemValue
User#1 of 1
User flags🔧
Session start2024-02-01 00:00:00
Session end2024-02-29 23:59:59
View range1M
User languagede_DE
User localede_DE
Locale(s) supportedde_DE.utf8: ✅
de_DE.UTF-8: ✅
User agentMozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0

Expected behaviour

Inverting the "has (any) category)" for a rule should match transactions.

Steps to reproduce

No response

Additional info

No response

@JC5
Copy link
Member

JC5 commented Feb 3, 2024

Alright, the test of the rule fails. That's not good! Does the rule itself work? When you actually run it?

@shrippen
Copy link
Author

shrippen commented Feb 3, 2024

Nope, doesn't work.

As a note - when I set up the rule without inversion and click on the little beaker icon in the rule overview it produces the search term has_any_category:true
If I invert the rule it produces: -has_any_category:""

The first one produces results, the second doesn't

@JC5
Copy link
Member

JC5 commented Feb 3, 2024

Thanks, I'll check it out!

@JC5 JC5 added the triage Still checking this out... label Feb 3, 2024
Copy link
Contributor

github-actions bot commented Feb 3, 2024

Hi there!

This is an automatic reply. Share and enjoy

This issue has been marked as being in triage. The root cause is not known yet, or the issue needs more investigation. You can help by sharing debug information (from /debug) if you also have this issue or when you haven't already done so.

Thank you for your contributions.

@JC5 JC5 added bug Verified and replicated bugs and issues. fixed Bugs that are fixed (in a coming release). and removed triage Still checking this out... labels Feb 3, 2024
@JC5 JC5 added this to the firefly-iii-v6.1.8 milestone Feb 3, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Verified and replicated bugs and issues. fixed Bugs that are fixed (in a coming release).
Projects
Status: Done
Development

No branches or pull requests

2 participants