Changing a schedule start date/repeat info resets spawn exceptions
-
Virgil DuprasIt seems, from the email Paul sent me, that the problem is, after all, that modified spawns are reset after a schedule Start Date change. I'm waiting for confirmation, but if it's the case, this wouldn't be a bug, but a feature request.
-
Virgil Dupras
- Title changed from Changing scheduled transaction detail changes reconciled to Changing a schedule start date/repeat info resets spawn exceptions
- Tag changed from bug, reconciliation to feature, reconciliation
-
Virgil Dupras
- State changed from new to accepted
It turns out that the real problem is that changing a schedule start date or repeat info resets all exceptions, which is a behavior as designed. The problem is that in a use case like Paul's where significant changes are made to spawns, that's a very annoying behavior.
This behavior exists because programmatically guessing what should be done with exceptions on start date or repeat info change is quite hard. A solution that Paul proposed would be that editing a spawn would automatically materialize the spawn.
It makes a lot of sense to me and I wonder why it wasn't like that from the start, but I still have to ponder about the implications of such a change first.
-
Virgil Dupras
- Tag changed from feature, reconciliation to feature
-
Virgil Dupras
- Tag changed from feature to feature, schedule
-
Virgil Dupras
- Assigned user set to Virgil Dupras
-
Virgil Dupras
- State changed from accepted to fixed
(from [1a252cb75224]) [#317 state:fixed] Materialize local schedule edits instead of creating exceptions in that schedule. https://bitbucket.org/hsoft/moneyguru/changeset/1a252cb75224/
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.