SUMMARY It would be great if there was an option somewhere in the KMM preferences to change the behaviour of KMM to not automatically/forcibly save payers/payees in the address book. CURRENT KMM BEHAVIOUR When writng a name into the "Payer/Payee" field of a transaction, KMM automatically shows a dialogue asking if this name should be added to the address book. By clicking on "YES", the name is saved to the address book as a new contact; by clicking "NO" the name is automatically deleted from the "Payer/Payee" field of the transaction. It is not possible to have a transaction with a name that is not in the address book. WISH An option in the KMM preferences that tells KMM to let the users write a Name into the "Payer/Payee" field of a transaction without forcing the user to create an address book entry for that payer/payee. In other words: Allow the user to have transactions containing names in the "Payer/Payee" field that are not in the address book. EXEMPLARY SCENARIO AND BENEFITS I buy and sell a lot of used items on various internet platforms and therefore send and receive a lot of transactions from/to a lot of other people. But about 99% of the people I trade with are "once in a lifetime" or "one time" contacts, meaning that I will have one transaction with them and then never again. But still those names clutter my address book. Right now I have about 1400 contacts/names saved in my address book, but only 15 to 20 of them have regularly/recurring transactions (like my health insurance company or my employer). Merging all of those "once in a lifetime" contacts into a "generic" contact like "private seller/buyer" is not a good option, because then I lose the names in case I need to search for a name at some point in the future. Benefit 1: Allowing the user to have transactions containing names in the "Payer/Payee" field that are not in the address book would declutter the address book and help to keep the overview. Benefit 2: I could have an address book entry of my close friend "John Doe" who I have many transactions with. This "John Doe" can be separate from a completely different "John Doe" who was a "one time" contact that I don't have in my address book. This way I would never get confused with two different people who have by accident the same names, because one (my friend) is in my address book and the other (one time contact) is not.
In addition to benefit 2 (see above): Benefit 2.1: I would be able to differentiate which transactions belong to my close friend "John Doe" and which belong to the one time contact "John Doe". Because those transactions I had with my friend are linked to his address book entry, the others are not. This would help a lot to avoid mixing up transactions from those two people.
I haven't looked in any detail, but I have never had KMM add anything to my addressbook. The question it asks me when I enter an unkown payee is whether I want to add it - if I say yes, it adds it to KMM's list of payees, but not to any addressbook. If you mean that you want to be able to have a transaction with a Payee that is NOT in the program's list of Payees, that will not happen, as Payees in transactions are only references to the ID of the Payee. One suggestion I can give is to create a Payee called "Misc Person" and then use that, keeping the exact name (if you do want to keep it) in the Memo. That is how I do most of the things I buy from eBay or pay for with PayPal. I also have thins like "Misc Food Store" for stores I don't use often enough to want to track separately. Can you please let us know if the problem still happens for you, which version of KMM you are using, and whether your really mean an addressbook, or just the internal list of Payees? Thanks
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!