Closed JLWade closed 6 months ago
Developer checklist added during refinement - starting with the simplest way to start.
Blocked until designs are added
Tested on TEST: Passed
Working as intended - moving to done.
@cameronpettit - I'm curious about the sticky function listed in the acceptance criteria, something to discuss and make a ticket around if necessary.
Moving back to in progress until timer is sticky and will remain in view as user scrolls down the page.
Sticky timer bar implemented.
Tested on TEST: Passed
Timer is now sticky - operating as intended, moving to done.
As a park visitor, I want to have confidence that if there are passes available when I start booking a DUP that I will be able to successfully book one.
Description:
One of the biggest pieces of feedback we get on DUP is that people try to book a pass and before they enter all their info and submit all the passes are sold out. Being able to hold your pass while you book for a specific amount of time would be ideal.
Acceptance Criteria:
Given I am a potential park visitor When I am on the booking page and select my booking date, facility, time and click
Reserve
Then I know my pass is "held" for me for 5 minutes or until I complete my booking within 5 minutes.Given I am a potential park visitor When I am filling out my information on the contact page Then I can see how much time I have to complete my booking before my pass goes back into the booking pool. [5 minutes]
Reserve
initiates an attempt to hold a pass, if successful, show the checkout screen. Otherwise 'no passes left'Development Checklist:
Reserve
Dependencies
Wireframe(s):
icon:
exclamation-circle-fill
background:#FEF1D8
text:#7E5D21
Workflows:
Definition of Ready (Note: If any of these points are not applicable, mark N/A)
Definition of Done
Notes: