-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Rules are not executed on FinTS import #2081
Comments
Hi! This is a canned reply that tells you how to get more debug details.
If you do not want to share log files or other details on Github, please send them to me over (encrypted) email. |
I'm pretty sure the FinTS import routine doesn't ask to apply rules. Hence, they aren't. I'll check if I can safely add it. I can't test this so I'm flying blind. |
I recklessly applied the patch to my 4.7.10 installation.
I'd say commit 2117fc2 is a success and closes this issue. |
Glad to hear it 👍. I'll close the issue when the new release is live. |
4.7.12 has been released. Follow the status of the Docker build on Travis CI. |
* develop: (26 commits) Slight change in build script. Updated meta files. New translations. Final touches for #2085 Extra debug log. #2061 Fix build script. Apply fix for #2070 Fix for #2070 Various code cleanup. Updates to the login procedure [skip ci] Push and build stuff. Update LDAP config for #2085 Updated LDAP code #2085 Fix issue with upgrade. Add required PHP extensions to composer.json. Code cleaning stuff. Fix for #2082 First part of a large code cleanup commit. Update version. Add thing to apply rules to fints #2081 ...
Bug description
I am running Firefly III version 4.7.10.
Whenever I import bank statements via FinTS my rules are not applied to the imported data.
I checked if rules "find" their corresponding and they match successfully. However, apparently none are executed.
Steps to reproduce
Expected behavior
Rules with matching transactions should be executed.
Extra info
I will add Logs as soon as I have any new transactions I can test this against
The text was updated successfully, but these errors were encountered: