Skip to content
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

Make changes to programslots more robust #8

Open
equinox0815 opened this issue Jul 9, 2017 · 1 comment
Open

Make changes to programslots more robust #8

equinox0815 opened this issue Jul 9, 2017 · 1 comment

Comments

@equinox0815
Copy link
Member

For now the only supported change to programslots is to define a later end dates. Any other case is either prohibited by the interface or does not what the user would expect.
The reason for this is that any other change would most probably mean that at least some timeslots needs to be deleted and possible recreated. Any notes added to those timeslots would be lost. In order to solve this pickle i propose the following:

  • after clicking 'save' in the edit show dialog the system should display any changes to timeslots and possible notes that must be made in order to fulfil the change request by the user.
  • this dialog should also offer possible conflict resolutions in case the newly generate timeslots overlap with existing timelsots from other programslots.
  • the user can then select a conflict resolution and confirm the transaction or click 'abort'
@eigenwijsje
Copy link
Contributor

@equinox0815: Challenge accepted!

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

No branches or pull requests

2 participants