[kmymoney] [Bug 443551] Default reconciliation state not used for new entries

[bugzilla_noreply at kde.org]

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

Brendan at CoupeWare.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Brendan at CoupeWare.com

--- Comment #2 from Brendan at CoupeWare.com ---
I always thought it meant the default state no matter how the transaction is
entered so clearing that up would probably help. I never enter transactions
while reconciling, so it appears that setting does nothing for me.

I guess it might help some to have that setting or a new setting define the
default state of transactions enter manually or when imported. I want
everything unmarked (not reconciled) so I'm okay with the current behavior.

I may be nitpicking, but "Default reconciliation state" seems a like it should
be "Default transaction state". Technically "Cleared" and "Not reconciled" are
both "Not reconciled". Seems like reconciliation state is binary.

This discussion of settings reminds me of an ongoing problem that I have with
matching when I import transactions. While the next tab over lets you set the
time frame for matching imported transactions, it does not work the way I
expect it to. There seems to be no limit on how far back matching to match the
transaction with the closest value which frequently screws up all of the splits
on paychecks. At the very least, the description should clarify what this
setting does. Ideally it would work on all imported transaction, or an
additional setting should be added to work on whatever this does not work on.
Maybe the ideal solution is to add this on a per payee basis since limiting the
time frame may only make sense on some payees.

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