Join GitHub today
Changed duration of a submission is not exported into new schedule #587
Changing the duration of a submission is possible by:
The currently set duration of a submission should be reflected in the backend planning view as well as in exports and the frontend. The WIP-view should show the currently set duration of the talk. Released schedules should show the duration that has been set at the time of the release of the schedule.
After changing the duration of a talk already placed in the scheduling view, the new duration is reflected in the scheduling raster but not in exports.
Steps to Reproduce
We changed the acceptable duration of some talks. As the new duration is shown in the backend we did not notice this producing conflicts in the frontend exports.
After changing the duration of a talk, remove it from the schedule pulling it into the unassigned talks row. Reschedule the talk pulling it into the previous spot of the time raster. Check and release schedule.
No, this is correct – once the talks have been generated, you'll have to move/modify them and then release a new schedule version for these changes to take effect. Our rule is to not modify existing schedule releases, because those are presumed to be static. This includes exports.
I agree that the WIP schedule slots should be changed, but I definitely do not want to touch existing schedules in such an update.
The schedule has been released with a new version number. The talk is part of the released version and has been switched over to the new submission type beforehand. Comparing frontend and backend views of the same version of the schedule different talk durations are presented:
I do understand it may be necessary to change this particular talk by setting a custom duration. We were just confused by the different output in front and backend view.