New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing a schedule start date/repeat info resets spawn exceptions #317

Closed
hsoft opened this Issue Jun 22, 2013 · 3 comments

Comments

Projects
None yet
1 participant
@hsoft
Owner

hsoft commented Jun 22, 2013

From GS

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.

@hsoft hsoft closed this Jun 22, 2013

@hsoft

This comment has been minimized.

Owner

hsoft commented Jun 22, 2013

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.

@hsoft

This comment has been minimized.

Owner

hsoft commented Jun 22, 2013

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.

@hsoft

This comment has been minimized.

Owner

hsoft commented Jun 22, 2013

(from [1a252cb75224]) [#317 state:fixed] Materialize local schedule edits instead of creating exceptions in that schedule.
https://bitbucket.org/hsoft/moneyguru/changeset/1a252cb75224/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment