Bug 442354 - When matching transactions, the first one selected should be first shown in the "Merge Transactions" dialog
Summary: When matching transactions, the first one selected should be first shown in t...
Status: RESOLVED FIXED
Alias: None
Product: kmymoney
Classification: Applications
Component: ux-ui (show other bugs)
Version: 5.1.2
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-12 20:55 UTC by Dawid Wróbel
Modified: 2024-07-08 16:41 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 5.2
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Dawid Wróbel 2021-09-12 20:55:09 UTC 
SUMMARY
When matching transactions, the first one selected should be first shown in the "Merge Transactions" dialog. This is how it used to work but it stopped most likely after most recent updates to the functionality.

STEPS TO REPRODUCE
1. Select 2 transactions that can be matched (i.e. same amount), the older one first and then the newer one, further down the ledger
2. Click match
3. Click merge

OBSERVED RESULT
The first transaction selected should be shown first in the "Merge Transaction" dialog, but instead the second one is.
Comment 1 TraceyC 2023-08-25 00:12:59 UTC 
Confirm that I can reproduce this bug in KMyMoney v 5.1.3
The dialog says the first transaction I selected is on top and will be used for the merged transaction.
In reality, the second transaction selected is in the first row and its information is incorrectly used for the merged transaction.
Comment 2 Jack 2024-07-06 18:29:28 UTC 
Hasn't this been addressed in the new ledger?  It is now possible to switch which transaction is considered "first" when merging.  If someone else can confirm, I'll be happy to close as fixed in 5.2.
Comment 3 TraceyC 2024-07-08 16:34:46 UTC 
Sorry for forgetting about this open case. The Merge Transactions dialog now behaves as I expect in KMyMoney 5.1.3
Comment 4 Jack 2024-07-08 16:41:14 UTC 
Thanks for confirming, but I didn't think this was fixed in 5.1.3, only in master branch.  Perhaps there was a partial fix in 5.1.3, which was enough to meet your needs, with further improvement of the match dialog in master branch, so I'll close as fixed in 5.2.