https://bugs.kde.org/show_bug.cgi?id=522428
--- Comment #1 from Jack <[email protected]> --- This is by design. When you create a new transaction in a ledger, the date is set to the date of the previously entered transaction. My understanding of the use case handled by this behavior is that people often enter multiple transactions for the same (earlier) date or close date range. If you are entering current transactions, you only have to enter one with the current date, and it should be set for the next one. Also, in case you are not aware, just typing "t" while the cursor is in the date field sets it to the current date. I'll leave open for now in case one of the developers has anything to add, but will probably close as "intentional." -- You are receiving this mail because: You are watching all bug changes.
