Bug 354674 - Unable to Match Transactions Where Both Account Transactions Imported or Entered by Hand
Summary: Unable to Match Transactions Where Both Account Transactions Imported or Ente...
Status: RESOLVED DUPLICATE of bug 33949
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.7.2
Platform: unspecified Microsoft Windows
: NOR wishlist
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-01 09:26 UTC by flywire
Modified: 2022-10-08 18:57 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description flywire 2015-11-01 09:26:51 UTC
"NOTE
The matching interface will not allow you to match two transactions which have both been imported.
Likewise, it won’t allow matching between two transactions which have both been entered by hand."

This is unreasonable because it is most likely that transactions will be entered by importing or by hand for most of the accounts. It needs fixing.

Reproducible: Always

Steps to Reproduce:
1. Import transactions for two accounts, or
2. Enter transactions for two accounts by hand.
Comment 1 allan 2015-11-01 11:12:21 UTC
Your wish is my command.

This was implemented in Master back in March and should be in the next stable release, coming soon-ish.

Matching is not a function of the CSV importer, but is part of KMyMoney itself, so I have amended the Component field on this bug report.
Comment 2 flywire 2015-11-01 11:18:52 UTC
Sounds good. Can you explain how the process would work? Is it feasible for a noob to run the master version you mention?
Comment 3 allan 2015-11-01 12:51:36 UTC
(In reply to flywire from comment #2)
> Sounds good. Can you explain how the process would work? Is it feasible for
> a noob to run the master version you mention?

As you are using the Windows version, this usually is based on Master when produced.  What is the date of your KMM?  If it is after 15 March 2015, or so, then it should have the fix, I think.  If before that, you could try downloading the current release.
Comment 4 flywire 2015-11-01 13:17:23 UTC
V4.7.2 Downloaded and installed 31/10/2015, kmymoney.exe dated 26/04/2015 A5:15AM.

Windows link on https://kmymoney.org/
Comment 5 flywire 2015-11-06 11:59:57 UTC
I think @allan is referring to this fix of author Thomas Baumgart Sat, 16 May 2015 06:20:41 +0000 (08:20 +0200): https://quickgit.kde.org/?p=kmymoney.git&a=commit&h=7a4901c668871882bba75068bf1256f2bf00dba0

Check in the next version.
Comment 6 allan 2015-11-06 13:08:23 UTC
(In reply to flywire from comment #5)
> I think @allan is referring to this fix of author Thomas Baumgart Sat, 16
> May 2015 06:20:41 +0000 (08:20 +0200):
> https://quickgit.kde.org/?p=kmymoney.

No, that doesn't seem to be relevant, but see https://bugs.kde.org/show_bug.cgi?id=333949 .
This includes matching both of manually entered and imported transactions.
The fix is in Master, and will appear in the next stable release, 4.8.

This has not yet been added to the Windows version.  It seems that development focus in on releasing Frameworks5/Qt5, which should also include the fix.


> Check in the next version.
Comment 7 Daniel Roschka 2017-08-01 15:10:23 UTC
Struggling with this issue too. Got two accounts with imported transactions, but haven't found a way to match them. Is that already working with 4.8.0 (Linux)? If yes how is the workflow for that supposed to be, as I even haven't found a way to display transactions of two accounts in parallel.
Comment 8 Jack 2022-10-08 18:57:14 UTC
The bug referred to in Comment 6 does seem to have resolved this problem, and I don't really see any difference, so I'm going to close this as a duplicate.  Given how old this fix was, I'd say to open a new bug if the problem is still present for anyone.

*** This bug has been marked as a duplicate of bug 33949 ***