GnuCash
Contact   Instructions
Bug 797115 - Can't 're-activate' an expired SX
Summary: Can't 're-activate' an expired SX
Status: NEW
Alias: None
Product: GnuCash
Classification: Unclassified
Component: Scheduled Transactions (show other bugs)
Version: 3.4
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: core
QA Contact: core
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-23 19:26 EST by Adrien
Modified: 2020-04-12 18:22 EDT (History)
4 users (show)

See Also:


Attachments

Description Adrien 2019-02-23 19:26:09 EST
I have a couple of SX that were set to run until a specified date. (also both were monthly if that matters)

The amounts for these two expenses change periodically. (one is for auto insurance usage that changes every 6 months, the other was for web services that changed at annual renewal)

I tried to reset both to be simple SX that recurred indefinitely. (and I'd just make it a point in the future to update the template accordingly) However upon exiting the SX Editor and then opening it back up again, both are set to 'never' as the next occurrence.

I've edited them back to 'Forever' several times with the same result. I've also tried exiting GC without re-opening the SX Editor, then restarting GC, but upon opening the SX Editor, both are back at 'never' as if I had not edited them. Note however that the new amounts in the splits of the template *are* saved, just not the recurrence setting.
Comment 1 Jean Laroche 2020-04-12 18:22:43 EDT
in trying to repro the bug, I'm finding a different, but also wrong behavior:
1) setup a monthly transaction that happens on the 12, starts on the 30th of this month (assume April for this discussion) and runs indefinitely. Save.
2) BUG: When you save it says in the scheduled transaction panel that the next occurrence will be 4/12 (should be May 12). In the transaction editor, the calendar shows the correct first date 5/12. 

I don't know whether this is related to what you saw, but I'll fix that, and then try to reproduce your bug.

Note You need to log in before you can comment on or make changes to this bug.