[kmymoney] [Bug 439532] Option to not automatically/forcibly include payees/payers in address book
https://bugs.kde.org/show_bug.cgi?id=439532 --- Comment #1 from MRib --- 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. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439532] New: Option to not automatically/forcibly include payees/payers in address book
https://bugs.kde.org/show_bug.cgi?id=439532 Bug ID: 439532 Summary: Option to not automatically/forcibly include payees/payers in address book Product: kmymoney Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: ri...@gmx-topmail.de Target Milestone: --- 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. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439377] Variables to fill in the "Memo" field (and other fields, too)
https://bugs.kde.org/show_bug.cgi?id=439377 --- Comment #3 from MRib --- Yes, a ITTT rules engine like you have suggested it in your linked post. Augmented by variables like I have suggested. If this would be a powerful engine like the one you have also linked in your post (https://lunchmoney.app/features/rules), then various fields could be modified by this engine, not being restricted to the Memo field. To make this optional as a plugin is a great idea. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439377] Variables to fill in the "Memo" field (and other fields, too)
https://bugs.kde.org/show_bug.cgi?id=439377 --- Comment #1 from MRib --- This could be combined with more advanced If-This-Then-That renaming rules, which would be a very very powerful feature of KMyMoney. A rule could structurally look like this: IF payee="My Insurance Company" THEN replace content of Memo field with "Health insurance fee %%.%mm%" -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439377] New: Variables to fill in the "Memo" field (and other fields, too)
https://bugs.kde.org/show_bug.cgi?id=439377 Bug ID: 439377 Summary: Variables to fill in the "Memo" field (and other fields, too) Product: kmymoney Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: ri...@gmx-topmail.de Target Milestone: --- SUMMARY It would be a very handy functional enhancement of KMyMoney if formulas and variables could be used to fill in the Memo field (and other fields, too). EXAMPLE My health insurance company debits 10$ from my bank account on November 1st 2020. Then I use aqBanking to sync my account. It would be great if I could define a formula including variables which is used to fill in the Memo field. The formula to fill the Memo field would look like this: "Health insurance fee %%.%mm%" The result in the Memo field would look like this: "Health insurance fee 2020.11" The variable %% would fill in the year and the variable %mm% would fill in the month when the debit occurred on by online bank account. This would be very handy especially with recurring transactions, because filling in a Memo could be automated with this approach and there would be no need anymore to fill in the Memo manually. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439376] New: Ledger: Option to show "Memo" field in the "Details" column
https://bugs.kde.org/show_bug.cgi?id=439376 Bug ID: 439376 Summary: Ledger: Option to show "Memo" field in the "Details" column Product: kmymoney Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: ri...@gmx-topmail.de Target Milestone: --- Created attachment 139788 --> https://bugs.kde.org/attachment.cgi?id=139788=edit Ledger with explanation of my request SUMMARY There should be an option somewhere in the KMyMoney settings/preferences that in ledger view, when transactions are displayed as single rows, the visible field in the "Details" column is the "Memo" field. This could be a global option or individually per ledger. Because in many cases the Memo can be more meaningful when searching for transactions than the payer/payee. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 435912] New: Add a filter-function to automatically assign transactions to categories and/or payees based on information in the "memo" field
https://bugs.kde.org/show_bug.cgi?id=435912 Bug ID: 435912 Summary: Add a filter-function to automatically assign transactions to categories and/or payees based on information in the "memo" field Product: kmymoney Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: ri...@gmx-topmail.de Target Milestone: --- SUMMARY Es sollte eine Filter-/Zuweisungsfunktion geben, die Text (exakt, teilweise, mit Platzhaltern *) im Feld "Notiz/Memo" erkennen und entsprechende Zuweisungen vornehmen könnte. Also z.B. WENN im Notizfeld "eBay*" steht, DANN weise die Überweisung der Kategorie "Privatverkäufe" zu. Denn wenn man z.B. bei eBay verkauft, dann ist der Zahler ja immer ein anderer. Mit solch einer Filterfunktion könnte man also eine Überweisung automatisch kategorisieren und müsste es nicht immer manuell machen. Die Zuweisung sollte nicht nur zu Kategorien, sondern auch zu Zahlern/Zahlungsempfängern möglich sein. Denn: Bspw. kann man mehrere Onlineangebote z.B. mit PayPal bezahlen: Online-Paketmarken von DHL, Hermes etc. Als Zahlungsempfänger steht dann immer PayPal auf dem Konto, aber das stimmt ja nicht, denn eigentlich bezahle ich ja zwei verschiedene Versandunternehmen, nur halt über denselben Zahlungsdienstleister (PayPal). In den Notizfeldern steht aber immer verschiedene Mandatsreferenzen. So könnte man dann anhand der unterschiedlichen Mandatsreferenzen die PayPal-Abbuchungen den Zahlungsempfängern "DHL" oder "Hermes" zuweisen, anstatt dass da immer nur PayPal steht und man nicht weiß, welche Abbuchung an welches Versandunternehmen gegangen ist. Einen kleinen Teil dieser Idee beherrscht KMM gegenwärtig ja schon. Man kann nämlich verschiedene Schreibweisen derselben Person im Feld "Name" demselben Zahlungsempfänger zuweisen lassen, also z.B. "Maria Müller" und "M. Müller" und "Mariechen Müller" alle zuweisen lassen an den Zahler "Schwesterherz". Wäre cool, wenn KMM in Zukunft auch das Feld "Notiz/Memo" auswerten und automatisch regelbasierte Zuweisungen zu Kategorien und/oder Zahlern vornehmen könnte. So könnte man also eine Regel erstellen, die nach einem beliebigen Text (es muss nicht auf Mandatsreferenz beschränkt sein) im Feld "Notiz/Memo" Ausschau hält und dann eine Zuweisung der Buchung zu einer Kategorie und/oder einem Zahler vornimmt. Eine solche benutzerdefinierte Automatisierung würde den Benutzern eine Menge manueller (Nach-)Arbeit abnehmen. SOFTWARE/OS VERSIONS Windows: 10 Pro x64 20H2 (but this is OS-independent) KMyMoney version: 5.1 (stable), Aqbanking6, Qt5.11, KF5.65 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 435911] New: Sort tags alphabetically in transaction details in ledger view
https://bugs.kde.org/show_bug.cgi?id=435911 Bug ID: 435911 Summary: Sort tags alphabetically in transaction details in ledger view Product: kmymoney Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: ri...@gmx-topmail.de Target Milestone: --- SUMMARY When adding tags to a transaction the tags are stored and displayed in the order of their entry, but not in alphabetical order. It would be more logical if tags would automatically be sorted in alphabetical order (just like in the "tags" section). Because tags are not hierarchical it makes the most sense to display them alphabetically in the transaction details in the ledger view section, too. STEPS TO REPRODUCE 1. Go to any ledger and edit a transaction entry by adding some tags. 2. Look at the sorting order of the tags. OBSERVED RESULT Tags are displayed in the order of the entry, not alphabetically. EXPECTED RESULT Tags should be sorted automatically in alphabetical order upon entry. SOFTWARE/OS VERSIONS Windows: 10 Pro x64 20H2 (but this bug is OS-independent) ADDITIONAL INFORMATION KMyMoney version: 5.1 (stable), Aqbanking6, Qt5.11, KF5.65 -- You are receiving this mail because: You are watching all bug changes.
