[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] Variables to fill in the "Memo" field (and other fields, too)
https://bugs.kde.org/show_bug.cgi?id=439377
Dawid Wróbel changed:
What|Removed |Added
CC||m...@dawidwrobel.com
--- Comment #2 from Dawid Wróbel ---
What you're specifically looking at is to schedule a recurring transaction with
such templated memo ("Health insurance fee %%.%mm%"), and then have
KMyMoney automatically match it each month after you download the transactions
with aqbanking.
I am not aware of templates taking variables at this point, but it is a
reasonable suggestion.
Regarding the ITTT rules engine:
https://invent.kde.org/office/kmymoney/-/issues/25
--
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.
