Bug 310671 - No payee name shown when asking for a new payee's default category
Summary: No payee name shown when asking for a new payee's default category
Status: RESOLVED FIXED
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.6.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
: 315369 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-11-25 20:21 UTC by Andreas
Modified: 2013-09-30 21:25 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.6.4
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas 2012-11-25 20:21:47 UTC
No payee name shown when asking for a new payee's default category

Reproducible: Always

Steps to Reproduce:
1. Under Configure KMyMoney > Ledger > Import activate the option "Ask for a new payee's default category"
2. Update an account with a aqbanking (will probably work with csv Import as well) making sure you do not have one of the payees being imported
3. The dialog with the category drop-down menu is shown saying "Please select a default category for payee" with no name of the payee being imported, so you actually cannot know which category should be chosen.
Actual Results:  
You can only abort or click on "No Category"

Expected Results:  
The name of the payee has to be shown in the dialog, so that the default category can be defined
Comment 1 Yözen Hernández 2013-05-18 01:09:01 UTC
This is one of the biggest annoyances for me with kmymoney. Don't get me wrong -- I love it and use it constantly to stay in budget.

But I also frequently connect to my bank with KBanking and imports QIF and OFX files. Every time I do, if I shopped at a new place or a different location for a chain, I get tons of new entries under Payees which are duplicates because the payee name is never shown on import, and lots of "uncategorized"  transactions.
Comment 2 Thomas Baumgart 2013-09-30 16:54:41 UTC
*** Bug 315369 has been marked as a duplicate of this bug. ***
Comment 3 Cristian Oneț 2013-09-30 17:02:29 UTC
This was fixed by Ralf in http://commits.kde.org/kmymoney/d457739d47a0fd7c767c1ecd400d35a7ce0df736
Comment 4 Andreas 2013-09-30 19:35:57 UTC
The status of the Bug was changed to RESOLVED and FIXED, but no Version provided in which the fix is going to be available. Can anyone take care of that?
Comment 5 Jack 2013-09-30 19:56:04 UTC
One of the developers would have to confirm it, but I think it is too late to add to 4.6.4.  It should go in 4.7, which does not yet have a scheduled release date.
Comment 6 Cristian Oneț 2013-09-30 21:25:05 UTC
(In reply to comment #5)
> One of the developers would have to confirm it, but I think it is too late
> to add to 4.6.4.  It should go in 4.7, which does not yet have a scheduled
> release date.

Actually this was also pushed in 4.6. So I marked it as fixed in 4.6.4.