Change schedule data on global scope edit
Reported by Virgil Dupras | May 26th, 2011 @ 02:07 PM | in v2.5 (closed)
From email:
When changing 'All future occurrences' the Scheduled transaction doesn't change. I would expect it to change and reflect what is currently happening without touching any older and/or reconciled occurrences of that transaction.
The problem is that global scope changes aren't necessarily made "from the start" and thus not all global changes should warrant a change to the schedule itself, but yeah, there should be a special case where globally changing the first spawn of a schedule changes the schedule itself.
Comments and changes to this ticket
-
Virgil Dupras January 24th, 2012 @ 10:40 PM
- State changed from “new” to “accepted”
- Milestone set to “v2.5”
- Milestone order changed from “195293” to “0”
-
Virgil Dupras February 1st, 2012 @ 06:53 PM
- Assigned user set to “Virgil Dupras”
-
Virgil Dupras February 2nd, 2012 @ 04:42 PM
- State changed from “accepted” to “fixed”
(from [fb634ecb7d07]) [#262 state:fixed] Schedules are now updated by global changes when appropriate.
When a global change becomes the first spawn of a schedule, it replaces the ref txn of the schedule. This is to avoid the confusing situations where the schedule transaction would be different from all its spawns, and that changing a schedule would have no effect on its spawn (a new global change would be required).
Also, deleting the first spawn(s) of a schedule will make its start date move forward.
https://bitbucket.org/hsoft/moneyguru/changeset/fb634ecb7d07/
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