Bug 341552 - When you set a memo for a transfer, it actually gets duplicated for each split, giving place to inconsistences
Summary: When you set a memo for a transfer, it actually gets duplicated for each spli...
Status: CONFIRMED
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: git (master)
Platform: Other All
: NOR wishlist
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-04 17:23 UTC by Alejandro
Modified: 2023-03-14 00:55 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alejandro 2014-12-04 17:23:56 UTC
When I create a transfer between two accounts, the memo introduced in one split is copied into the memo for the second split. This is inconvenient, as if I decide to change the first one (e.g. due to a typo), the second one does not change.

This does not happend with accounts and categories, though.

Reproducible: Always

Steps to Reproduce:
1. Create a transfer between two account A and B, setting "typppo" as memo.
2. Realize "typppo" was a typo, and change the memo in account A.
3. Go to account B and realize the type is still there.

Actual Results:  
You have to change both memos.

Expected Results:  
You wouldn't need to do such thing when not an split transaction.
Comment 1 Christian David 2015-01-04 18:17:54 UTC
Giving the chance to have different descriptions is a intended feature. If you download the transactions from a bank, they are almost always different. If we change that behavior, a new method to handle the case I described is needed.
Comment 2 Jack 2023-03-14 00:55:11 UTC
I believe we need to revisit how memos are (or are not) changed.  It is now possible to have a transaction with three different memos - one for the transaction, and two different ones for the splits.  In this case, there is no way to edit the transaction memo.  I'm adjusting version and platform, and changing to a wishlist, as the problem is an inconvenience, but doesn't endanger any data.