https://bugs.kde.org/show_bug.cgi?id=479131
Szőts Ákos <szots...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REPORTED
Resolution|WORKSFORME |---
--- Comment #4 from Szőts Ákos <szots...@gmail.com> ---
I did some more financial accounting in KMyMoney which involved scheduled
transactions and I figured out what is the issue.
When you create a new scheduled transaction, the window has the defaults
already filled out. This includes the one month frequency setting and the T+1
month as the next occurrence date pre-filled.
However, when you change the frequency to something else than exactly one
month, e.g. to one year, the next occurrence date won't change, it still stays
as today + 1 month.
The problem is that the correction from the user side is not automatic (and
also not apparent that it has to be made; this is why this bug report was born
in the first place).
The user has the following choices:
- Calculate themselves manually when the next occurrence will happen, including
bank holidays, etc and put that value in. This can be done by KMyMoney in other
cases.
- Set the next occurrence date back to today, and cancel today's event manually
in the ledger. This way the next real occurrence will be automatic (my
solution).
All of these depend on that the user noticed that the next occurrence date
became invalid at the point when they changed the frequency or the frequency
value.
If the next occurrence is in less than one month, KMyMoney will probably skip
that, too, until T+1 month kicks in.
--
You are receiving this mail because:
You are watching all bug changes.
