https://bugs.kde.org/show_bug.cgi?id=359874
--- Comment #2 from lwilson1...@cox.net --- My .kmy file contains several years of my financial history. I'm not going to upload it to a public Bugzilla. I'd send you an "anonymous file" version of it, but since that would change all of the payee names, it would render it essentially useless for diagnosing this issue. I realize that makes it much more difficult for you to help me, but I'm not comfortable making that much personal data public. If it helps to quantify the term "most," I just imported 25 transactions today, and 2 of them matched. Only 6 new payees were created. I then had to manually match 19 transactions which would have been automatically matched before this bug was introduced. This is about par for the course. Each pair of transactions I manually matched were within 30 days of each other. I don't have time right now to check every one, but at least two or three of the payees involved had payee matching disabled. How hard would it be to add a global setting to turn off payee matching? CSV imports worked great until that was introduced. As of this writing, I am still running KMyMoney 4.7.2. -- You are receiving this mail because: You are watching all bug changes.
