[kmymoney] [Bug 359874] Most imported transactions not automatically matched with payee matching off
https://bugs.kde.org/show_bug.cgi?id=359874 NSLW changed: What|Removed |Added CC|lukasz.wojnilow...@gmail.co | |m | -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 359874] Most imported transactions not automatically matched with payee matching off
https://bugs.kde.org/show_bug.cgi?id=359874 lwil...@wiaw.net changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #16 from lwil...@wiaw.net --- Thank you, your changes to the sample file gave me a few more clues as to how the payee matching syntax works. It still didn't answer all my questions, though, and I'd still like to see some documentation. For example, do I have to escape out asterisks? I applied what I learned to my personal kmymoney file, and it didn't work reliably. One or two patterns that only had letters and a single space worked, while many others fitting that same description didn't. I don't have access to my file at the moment, but when I do I'll try to find some examples that I'm comfortable sharing. I assume in your testing with that sample file, your reproduced the original issue on the current version of kmymoney, so I've marked the bug REPORTED again. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 359874] Most imported transactions not automatically matched with payee matching off
https://bugs.kde.org/show_bug.cgi?id=359874 --- Comment #15 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 359874] Most imported transactions not automatically matched with payee matching off
https://bugs.kde.org/show_bug.cgi?id=359874 --- Comment #14 from Thomas Baumgart --- Created attachment 153624 --> https://bugs.kde.org/attachment.cgi?id=153624=edit Fixed Fictional KMY file I attached a 'fixed' version of your fictional file. I added the necessary regex to the payees so that matching can happen. Except two, they all match on the full name. Exceptions are "Bob's House of cards" and "Joe's" which only requires the lead-in of the imported payee name to match. I have checked this against https://binary-factory.kde.org/view/AppImage/job/KMyMoney_Release_appimage-centos7/lastStableBuild/ and my development build (based on master). It matches 5 of your 6 transactions in the CSV. The one that is not matched is due to the different sign of the amount. Once you change the sign it matches it as well. When importing the file a second time all transactions are detected as duplicates. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 359874] Most imported transactions not automatically matched with payee matching off
https://bugs.kde.org/show_bug.cgi?id=359874 --- Comment #13 from lwil...@wiaw.net --- If this is "working as designed", could you please provide some documentation on how it's designed? I haven't tried in a while, but every time I try to set up payee matching, it goes horribly wrong - possibly because I have no idea how the "regular expression" syntax is supposed to work. I've been matching every transaction manually for so long that I'm almost used to it, but it still bothers me because I know it could be so much easier. Please don't use the argument that "it's been so long, it's not worth fixing it now," because I've been asking for this since the first broken version came out. I can reproduce the behavior in the current version of kmymoney, but please be patient with me; I'm very busy and can't devote a lot of time to this (especially since the bug is costing me time every month). If I had more time, I'd figure out how to write a fix myself. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 359874] Most imported transactions not automatically matched with payee matching off
https://bugs.kde.org/show_bug.cgi?id=359874 --- Comment #12 from Jack --- I don't recall when this was originally filed, but it seems to me KMM is acting as designed. If I have an imported transactions with the same amount, close date, but different name/payee, I personally would NOT want it to match an existing transaction. If I did want it to match, I would use the matching tab in the Payees View. My remaining question is how the matching was done prior to the change introduced in 4.7.1. However, it's now so long ago, reverting is not really an option, so at best, this might be converted to a wishlist requesting the ability to configure things so the matching behaves as it did prior to 4.7.1, with a clear description of the new criteria for matching in such cases. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 359874] Most imported transactions not automatically matched with payee matching off
https://bugs.kde.org/show_bug.cgi?id=359874 Justin Zobel changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #11 from Justin Zobel --- Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! -- You are receiving this mail because: You are watching all bug changes.
