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

--- Comment #2 from surcouf <arnaudvillem...@gmail.com> ---
(In reply to Jack from comment #1)
> First, KMyMoney does not currently track the creation date of Payees, so 
> including this would involve more than a (hoopefully) simple GUI enhancement.
Ok. Should i open another wishlist item regarding the database of KmyMoney?
like "introduce new database fields: 
- date of payee creation (type=Timestamp)
- channel of payee creation (Type=text)
      with these members (my suggestions):
               - created by manual user data-entry
               - created through manual user data import
               - created through account synchronized data import

> I'm just musing here, but would these additional fields go an a new tab (what 
> would it be called?)  Might it be reasonable to create a "Additional 
> information" tab 
yes, a new tab is a good idea. Called "payee statistics"?

> to include this new information plus what is currently on the Default 
> Category and Account Numbers tabs? 
not if the new tab is called "payee statistics" :) but otherwise, why not.
on the other hand, i like the current tab names, because they are very precise.
Merging "Default Category" and "Account Numbers" would be a "intuitive
navigation loss" there...

> (I think the Transactions, Address, and Matching tabs are likely to be too 
> large to merge. 
i agree

> Separately, are any of these reasonable to put in an additional  column in 
> the Your payees list?
Yes, that is also a good idea and avoids the questions around new tabs or
changing existing tabs.

> There is an additional issue, that Payees can actually be specified on both 
> Transactions and Splits.  I don't know how easy or hard it would be to 
> calculate the value to be added when the Payee is listed on the transaction, 
> since it clearly is not the sum of all splits.
I am not sure i understand your point. My understanding of transaction split it
that the total transaction amount may be split on distinct categories, but NOT
on distinct payees. Therefore all splits of 1 transaction stay booked on 1
single payee. Why should this be an issue to sum up the amounts by payee?

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

Reply via email to