[Kmymoney-devel] [kmymoney4] [Bug 339175] Multiple selection of transactions for "matching" not allowed, and transactions don't match automatically on OFX direct download

[Mike Wolfe]

https://bugs.kde.org/show_bug.cgi?id=339175

--- Comment #2 from Mike Wolfe <wolfemi1 at gmail.com> ---
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 at gmail.com> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |onet.cristian at gmail.com
>               Status|UNCONFIRMED                 |NEEDSINFO
>           Resolution|---                         |WAITINGFORINFO
>
> --- Comment #1 from Cristian Oneț <onet.cristian at 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.
>

-- 
You are receiving this mail because:
You are the assignee for the bug.