Summary: | Multiple selection of transactions for "matching" not allowed, and transactions don't match automatically on OFX direct download | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | Mike Wolfe <wolfemi1> |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | onet.cristian |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | http://commits.kde.org/kmymoney/5277848b040237b81aac9d31a09299c523b33d82 | Version Fixed In: |
Description
Mike Wolfe
2014-09-18 13:50:52 UTC
About the first problem: transaction matching code was refactored since the 4.6 series so it would be nice if you could create a simple testfile to reproduce the behavior that used to work on 4.6.4 but does not work in 4.6.90-cdd451fe35; otherwise this will be released as 4.7.0. We would need a KMyMoney testfile with proper matching rules setup and a test import file which contains a transaction that used to match in 4.6.4 but is not matched any longer. About the second problem: I need to take a look at it, it should work. Christian, Thanks for the reply! For the first problem, I was unable to reproduce it with proper matching settings applied. Maybe it was a one-off, I don't know, but I don't consider it an issue unless I see it again later. For the second one, I'm seeing some stranger behavior. I am able to select multiple ledger entries of any one type, by which I mean manually entered or direct downloaded entries (e.g. I can select two, five, or ten manually input transaction, or six downloaded transactions). However, I can't select from BOTH of the two groups, which makes matching impossible. -Mike On 9/23/2014 8:20 AM, Cristian Oneț wrote: > https://bugs.kde.org/show_bug.cgi?id=339175 > > Cristian Oneț <onet.cristian@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |onet.cristian@gmail.com > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Cristian Oneț <onet.cristian@gmail.com> --- > About the first problem: transaction matching code was refactored since the 4.6 > series so it would be nice if you could create a simple testfile to reproduce > the behavior that used to work on 4.6.4 but does not work in 4.6.90-cdd451fe35; > otherwise this will be released as 4.7.0. > > We would need a KMyMoney testfile with proper matching rules setup and a test > import file which contains a transaction that used to match in 4.6.4 but is not > matched any longer. > > About the second problem: I need to take a look at it, it should work. > I need to check if this is not by, any chance, caused by the fix for BUG 335122, which does not allow the selection of register entries of different types. Git commit 5277848b040237b81aac9d31a09299c523b33d82 by Cristian Oneț. Committed on 23/09/2014 at 20:25. Pushed by conet into branch 'master'. Allow matching again by selecting imported and local transactions. This has been broken by a previous fix for Related: bug 335122 M +3 -10 kmymoney/widgets/register.cpp http://commits.kde.org/kmymoney/5277848b040237b81aac9d31a09299c523b33d82 |