[Kmymoney-devel] [kmymoney4] [Bug 333949] New: kmymoney won't match or allow manual matching on two imports or two manual transactions

[Chris]

https://bugs.kde.org/show_bug.cgi?id=333949

            Bug ID: 333949
           Summary: kmymoney won't match or allow manual matching on two
                    imports or two manual transactions
    Classification: Unclassified
           Product: kmymoney4
           Version: git master
          Platform: unspecified
                OS: other
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: kmymoney-devel at kde.org
          Reporter: developerchris at rebel.com.au

When importing from two different sources (csv) transactions are not matched.
Manual matching is disabled.

While it is known that this is by design. The recent conversation on
kmymoney-devel has not produced a reason for this design choice.

As more and more transactions are entered by importing only, this is very
inconvenient. 

An example is when importing both credit card statements and then bank account
statements. payments from the bank account onto the credit card (using payee
assignment) are not matched and cannot be manually matched. This leaves the
credit card balance to be incorrect.

Reading the documentation says deleting one of the transactions rather than
matching can result in an error. but as manual matching is not available you
have little choice.

Disabling the checks surrounding this 'bug/feature' allows the transactions to
be manually matched without apparent side effect.

Recommended fixes include 

1/ Disabling the checks when manually matching and allow the transactions to be
matched, as the user has to decide to do this, this should not be a problem.

2/ Removing the restrictive code and allow matching to proceed even when both
transactions are imported (but have separate sources as in my example)

3/ Same as 2 but popping up a message to ask if this is required. This may
resolve edge cases.

As this is a design choice it would be nice to know why the decision was made
If my above three choices doesn't cover the reason another arrangement may
work.

Reproducible: Always




This bug is related to
https://bugs.kde.org/show_bug.cgi?id=278753

-- 
You are receiving this mail because:
You are the assignee for the bug.