-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Description based rules breaking with (space) usage. #7609
Comments
I can't replicate this. On the demo site, using "daily shot" as the trigger value works fine. |
If your bank adds many spaces, that could be the problem. They are generally not visible in HTML but they may show up when you edit the transaction. |
You means many spaces on description? But, even trying "description contains" and "description starts" with only " Oh maybe I found the problem... I make some test 👍🏻 |
Mmmmmm seems problem is on date range or account id..
The differences are operator (applied only on
|
I see what you mean, it's a problem in the test / execute form. I'll pick it up! |
I've tested and I confirm is fixed 👍🏻 |
Hi there! This is an automatic reply. This issue is now 🔒 closed. Please be aware that closed issues are not watched.
Thank you for your contributions. |
Support guidelines
I've found a bug and checked that ...
Description
I have a set of rules in which I specify the contents on the description, (either with "description is" description contains"), and some simply do not work at all.
Eg, "The bank transfer".
Expected behaviour: Descrition is "The bank transferr" = detection
Actual behaviour: Doesn't recognize any transaction with this description.
Workarround:
Description contains: "The"
Description contains: "bank"
Description contains: "transfer"
I can't be sure when this problem arrised.
Debug information
Debug information generated at 2023-06-06 00:00:00 Europe/Lisbon for Firefly III version 6.0.10.
8.2.6
Linux
192.168.1.83
Expected behaviour
No response
Steps to reproduce
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: