Reported on web as bug 293405. If you enter a transaction in the default order, tabbing between cells, the date will go red and the error message is displayed. To stop / fix the problem the category must to be edited with a date prior to the transaction date that is being entered. If however, you enter the transaction in reverse order the date will flash red, but the transaction will enter and the category date will be set to the transaction date. Reproducible: Always
The bug you refer to happened due to the user expecting MM-DD dates, but the system was set to DD-MM (or perhaps the other way around) and was closed as "NOT A BUG" Also, since 4.7.2, there have been changes made to avoid this type of error. Unless someone claims this is still a problem, I'm going to close it as fixed, or perhaps UNSUPPORTED.
Can you confirm this still happens with 5.x or at least 4.8.x? Also, can you specify what exactly you think is wrong, and what you think the correct behavior should be?
I actually can't remember the exact issue from almost 4 years ago. However, I cannot remember the issue happening in the resent past. -----Original Message----- From: Jack <bugzilla_noreply@kde.org> Reply-To: bug-control@kde.org To: john.koch7@verizon.net Subject: [kmymoney] [Bug 349625] Entering transaction into ledger creates error message "cannot enter transaction with post date prior to opening date" Date: Mon, 06 May 2019 16:56:30 +0000 https://bugs.kde.org/show_bug.cgi?id=349625 Jack <ostroffjh@users.sourceforge.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WAITINGFORINFO CC| |ostroffjh@users.sourceforge | |.net Status|REPORTED |NEEDSINFO --- Comment #2 from Jack <ostroffjh@users.sourceforge.net> --- Can you confirm this still happens with 5.x or at least 4.8.x? Also, can you specify what exactly you think is wrong, and what you think the correct behavior should be?
Thanks. I'll close as FIXED. I believe the issue was about creating transactions prior to the opening date of either the account the transaction was in OR the account of the category. The order of specifying the date and the category for the transaction may well have determined whether or not an error was displayed. Anyway, since then, there have been several enhancements regarding that date issue, and at least one of them probably did fix what you saw. I wish I could specify the Version Fixed In, but I'm not even sure if it was a 4.8 or a 5.0 version, so I'll leave that blank.
To me this looks like it has been fixed with https://cgit.kde.org/kmymoney.git/commit/?id=7a4901c668871882bba75068bf1256f2bf00dba0 which references bug 313793 (so maybe it is a duplicate). Anyway, the above fix first appeared in 4.8.0