[Kmymoney-devel] [Kmymoney2-developer] [kmymoney2] [Bug 213250] QIF Import creates numerous Unneeded Accounts

[Jack]

[trying to keep primary thread on newer list]

On 2014.07.17 13:42, Allan wrote:
> On 17/07/14 15:14, Jack wrote:
> > On 2014.07.17 03:00, Cristian Oneț wrote:
> >> https://bugs.kde.org/show_bug.cgi?id=213250
> >> --- Comment #6 from Cristian Oneț <onet.cristian at gmail.com> ---  
> While
>>> working on BUG 337251 I noticed that the fix for this bug will  
>>> cause the brokerage account to not be created when importing this  
>>> file https://bugs.kde.org/attachment.cgi?id=87747 leaving the  
>>> transaction unassigned. While on 4.6.x the brokerage account is  
>>> created and the transaction is assigned. I tend to think that the  
>>> 4.6.x behavior is the expected one, could someone with more  
>>> QIF/investments knowledge confirm this?
> >
>> How does this relate to the issue that kmm will only assign such  
>> transactions to the brokerage account if it has the default name?  
>> (Including the "(brokerage)")?   There is (or should be) a wish list  
>> posted to have KMM remember the brokerage account assigned at  
>> account creation time, no matter what the name (such as if using an  
>> existing checking account).  Or - is this bug only about creating  
>> the brokerage account on the fly if it doesn't exist?
> >
> > Jack
> 
> We have two slightly related bugs intertwined here.  BUG 337251  
> mentions a bunch of things, including automatic creation of  
> "(brokerage)" accounts.  BUG 213250 contained the fix for the  
> unnecessary creation of them.
> 
> Allan

I'm just hoping/suggesting that any new fix for either of those  
consider the request that if an account with a non-default name is  
indicated when the investment account was created, that it be used  
unless a different account is explicitly included in the imported  
transaction.  Since I don't know the underlying code, I have no idea  
what the implications of that request are on fixing this bug.   
(Fortunately, I see that the bug against KMM-2 is marked solved, so I  
assume any current actions will be against the newer bug.)

Jack