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

Event times #195

Open
JB62 opened this issue Jun 3, 2017 · 0 comments
Open

Event times #195

JB62 opened this issue Jun 3, 2017 · 0 comments
Labels

Comments

@JB62
Copy link
Collaborator

JB62 commented Jun 3, 2017

It is currently possible to create events with zero duration, or events that overlap. While this in itself isn't a problem, the start and end times are critical when allocating vehicles to an event. It should not be possible to allocate a vehicle to an event or duty such that it has to get from one to the next in less time than would be available. If it's at an event in Corby until 5.30pm, it can possibly be allocated to a duty rider in Reading to start at 6pm for instance.

We discussed some sort of fixed time periods along the lines of am, pm or evening where these reflect the current split of controller times of 8-1, 1-7, 7-8. The start/end data could still be stored as datetime values, albeit with fixed times, in the back end, but would be shown to the user as simply as starting/ending AM, PM or Evening This means an event could span any one or several periods but that would set the start and end and thus align with duty allocations.

@pjfl pjfl added the wishlist label Jun 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants