Skip to content
This repository has been archived by the owner on Aug 3, 2022. It is now read-only.

Handle conflicting appointments #59

Open
agentphoenix opened this issue Mar 21, 2014 · 0 comments
Open

Handle conflicting appointments #59

agentphoenix opened this issue Mar 21, 2014 · 0 comments

Comments

@agentphoenix
Copy link
Owner

Overview

Update the availability and booking engines to handle conflicts.

Requirements

  • For recurring services, check each date and if there is a conflict, give the user credit for that date and don't book the event.
  • In the event that more than 50% of the instances have conflicts, do not allow the user to book and notify them there are too many conflicts.

Requires #24 to be completed first.

Estimate

20 hours

@agentphoenix agentphoenix added this to the Release 2 milestone Mar 21, 2014
@agentphoenix agentphoenix changed the title Conflicting appointments report Handle conflicting appointments Mar 31, 2014
@agentphoenix agentphoenix removed this from the Release 2 milestone Apr 3, 2014
@agentphoenix agentphoenix modified the milestone: New Booking Process Mar 3, 2015
@agentphoenix agentphoenix modified the milestones: New Booking Page, BookNow 2.0 Jul 24, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant