Should editing multiple transactions allow adding a tag?
Ingo Klöcker
kloecker at kde.org
Mon May 26 19:27:19 BST 2025
On Montag, 26. Mai 2025 19:59:34 Mitteleuropäische Sommerzeit Thomas Baumgart
via KMyMoney-devel wrote:
> On Montag, 26. Mai 2025 18:59:18 CEST Jack wrote:
> > Less related to this bug than to other recently filed/closed bugs about
> > tags, I note that both the transaction itself and each split has a
> > memo. Currently, only splits have tags. Might it make sense to allow
> > tags on the transaction itself as well as on each split? If so,
> > however, we have the same problem about how to easily edit them.
>
> Actually, I want to eliminate the memo in the transaction. This comes
> a very long way (almost 25 years) and I don't know if it is still used
> at all or can be replaced with the one in the splits.
I'm using the memo of the transaction a lot for transactions with splits. The
most important example is invoices paid to me with VAT. Those transaction are
automatically converted to a transaction with two splits. (By the way, very
convenient feature.) The invoice number that I put in the memo belongs to the
entire transaction and not to an individual split. Same for something like
income tax transactions where I use splits for the different tax amounts
(income tax, Soli), but the common memo "Einkommensteuervorauszahlung".
I don't think that I created many transactions with a memo on the transaction
and additional memos for the splits. So, it would probably be okay if the
transaction memo is stored as common memo for the splits. But I fail to see
what you gain by this.
> Creating a tag for the transaction will not only be confusing while
> entering data but also in the reporting section.
I don't see the problem. I'd expect a tag for a transaction with splits to be
treated as common tag for all splits. It'd be inconvenient if one had to add
the same tag to all splits.
In general, anything entered at transaction level is common for all splits and
everything entered for an individual split is (obviously) not common for all
splits. The value for a split would be the combination of the common value for
the transaction and the individual value for the split.
Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kmymoney-devel/attachments/20250526/8d07a642/attachment-0001.sig>
More information about the KMyMoney-devel
mailing list