I've been testing v4.7.2 for a few days and I noticed it's now impossible to enter the same value in the No. field for more than 1 transaction.
While this could be the expected behavior for a check number which obviously cannot be used twice, I've always used the No check field in KMM for other purpose, e.g. method of payment or the date for a deferred debit card. Now when entering a same value KMM asks whether to increment this value and if the answer is NO, the field is automatically cleared and the transaction is entered with an empty No. field.
Does anybody knows if there is a way to bypass this annoying (mis)behaviour?
Should I report a bug?

(Oh and yes I tried every possible check/unckeck in the Data entry settings of KMM, like auto-increment, insert type into No. field....etc..)

Are you sure? I tried it in 4.6.4 and while KMM does mention the number is already used and asks if I want to replace it with the next available number, it does accept the duplicate if you reply "no" to the question. So, I now have two transactions with the same number in my account.

BTW, I would not consider this a bug. You are in fact abusing the intent of the functionality. It is better that the software detects and, if dangerous, prohibits abuse. For instance, it could be that altering the transaction number messes up transaction matching during import. I don't know if this is so, but if it were, I'd say that correct matching is way more important than allowing to hack the transaction number.

@ zebulon
Yes you're right. As I said "it's NOW impossible to enter the same value", I meant that BEFORE (version 4.6.6) that was possible.
Unfortunately KMM does not have any field to input additional data like payment methods. Even in the KMM Handbook they say you can set the check nr field always visible, so that you can use it for other purposes instead of an increasing check number.
In the ledger settings you can also check an option to automatically "Insert transaction type into No. field".
If this field was exclusively reserved for cheques numbers I would agree with you, but that's not the case.

Your reply made me fear I overlooked something. Both the 4.6 and 4.7 handbooks say textually the exact same thing. Interesting is that the term "check number" is used, while it should really be "transaction number" since it is an attribute of all transactions. However, there is only one numbering system. You cannot have both a check numbering and, e.g. an independent money transfer numbering system.

Code: Select all

The check number can be entered if needed. Note that the check number can always be visible if desired. This is configured in the Settings dialog.

While this does not support your claim that the check number can be used for other (non numbering) purposes, I went through the 4.7 change logs and found this:

Code: Select all

2014-01-26 10:49:42 +0000 Allan Anderson
 * BUG:319801 - Fix losing track of check number if check number sequence is
interrupted. REVIEW:115302

2014-01-27 11:09:56 +0000 Allan Anderson
 * BUG:319801 - Fix losing track of check number if check number sequence is
interrupted. (Part 2) REVIEW:115338

2012-01-29 12:33:14 +0100 Thomas Baumgart
 * Support more number formats for check numbers

Bug 319801 is related to your idea of using the transaction number for other purposes than a check number, and the bug fix is probably what explains the behavior you saw, although its purpose was in fact to allow exactly what you want to do. Please read the Bug #319801 log. You can comment on that page if you think the provided fix is not working as intended.

Yes I noticed that when entering a non-numeric note in the ledger number field, KMM loses track of the next check number. That was a minor annoyance to me. I don't know if the fix they provided is related to this new behavior of forcing a blank field.
For the time being I've stopped using v4.7.2 in favour of 4.6.6 and filed a new bug: https://bugs.kde.org/show_bug.cgi?id=360500