Changing a schedule start date/repeat info resets spawn exceptions
Reported by Virgil Dupras | March 23rd, 2012 @ 05:07 PM
I made changes to the scheduled transaction reflecting my regular salary. That transaction always has a few minor changes so I leave the text "est" in the check number field until I enter those adjustments. I recently changed the schedule transaction details but did not change the start date and as a result the older reconciled transactions all changed to the new values (loosing all the individual changes in the process) beginning with the start date. This was true for reconciled transactions. I am still in the camp that if a transaction has been reconciled then nothing should change it automatically.
EDIT: The nature of the ticket changed, see comments below.
Comments and changes to this ticket
-
Virgil Dupras April 5th, 2012 @ 09:22 PM
It 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 April 6th, 2012 @ 05:44 PM
- 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 April 6th, 2012 @ 05:49 PM
- 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 April 6th, 2012 @ 05:54 PM
- Tag changed from “feature, reconciliation” to “feature”
-
Virgil Dupras April 6th, 2012 @ 05:55 PM
- Tag changed from “feature” to “feature, schedule”
-
Virgil Dupras September 28th, 2012 @ 03:42 PM
- Assigned user set to “Virgil Dupras”
-
Virgil Dupras September 28th, 2012 @ 05:21 PM
- 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.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Virgil Dupras