I agree, the behavior should not be changed, but perhaps the UI could be
improved if people aren't realizing what is going on.
Of course, there is a responsibility for the user to learn the software,
how it works, and pay attention to things. (such as noticing last run
and next occurrence dates)
It is also a good idea to be familiar with preference settings. There's
no reason you *have* to let GnuCash auto-create SXs without telling you.
You can request a notification, and you can require that each one gets
approved first. (and of course, you can still edit or delete them at any
time)
I'd say the feature is working as intended. If you want it to 'resume'
but not 'catch up' then change the start date.
There might be very good reasons why someone would pause an SX and want
it to fill-in past instances after un-pausing. Testing, troubleshooting,
verifying something, trial scenarios, et cetera come to mind off the top
of my head.
Regards,
Adrien
On 4/12/22 4:06 PM, David Carlson wrote:
When you open the scheduled transaction in the transaction editor, you get
hit in the face with the listing of the last occurred date under the
Occurrences section. I think that pretty obviously suggests that the next
occurrence will follow the defined sequence from that date unless it is
edited. Further, in the Scheduled Transactions list there is a column
titled Next Occurrence. I wonder what date is listed there?
The most one could ask for is minor updates to the UI to make that even
more obvious.
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
