Summary: | Variables to fill in the "Memo" field (and other fields, too) | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | Unknown <null> |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | REPORTED --- | ||
Severity: | wishlist | CC: | me |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Other | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Unknown
2021-07-01 17:10:14 UTC
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 %yyyy%.%mm%" What you're specifically looking at is to schedule a recurring transaction with such templated memo ("Health insurance fee %yyyy%.%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 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. |