On Montag, 26. Mai 2025 20:27:19 CEST Ingo Klöcker via KMyMoney-devel wrote:
> 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". Fair point. > 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. That might be the problem/area of misunderstanding/tricky part: using the transaction editor the user in fact edit two splits at the same time. The memo is stored with both splits, the tag is only stored with the split of the counter account (for reporting reasons). Why is it the way it is? Historical growth covering a few diverse use cases. -- Regards Thomas Baumgart ------------------------------------------------------------- Q: What did the drummer name his twin daughters? A: Anna one ... Anna Two ... -------------------------------------------------------------
signature.asc
Description: This is a digitally signed message part.
