As a Park Operator, I want to have a frictionless experience when entering my Attendance and Revenue numbers, so I can complete my work quickly and without stress.
Acceptance Criteria
The AC below would all improve the user experience for our Park Operators. This ticket includes time for exploration into how much time it might take to implement each of these. If any are going to take a long time / custom code, please note that in this ticket and bring it back to stand-up for discussion.
Up/down arrows from fields are not present. (There is no use case for these as the numbers being entered will generally be quite large – so these arrows just add to visual noise without adding useful functionality.)
Fields do not allow entry of negative numbers. see potential solution (No use case for this as A&R numbers are never negative. Disallowing negative numbers will help us remove an error case that prevents the users from moving forward. Error messages will need to be implemented if we can’t prevent this.)
Attendance fields do not allow decimals. (These fields are for counting people and cars so whole numbers only are needed. Error messages will need to be implemented if we can’t prevent this.)
Revenue fields are limited to 2 decimal places.
On click of a field, whether it displays “no data” or has a value entered in it, that value should be highlighted by the click, so that, when the user types, they automatically overwrite the previous value.
Description
As a Park Operator, I want to have a frictionless experience when entering my Attendance and Revenue numbers, so I can complete my work quickly and without stress.
Acceptance Criteria
The AC below would all improve the user experience for our Park Operators. This ticket includes time for exploration into how much time it might take to implement each of these. If any are going to take a long time / custom code, please note that in this ticket and bring it back to stand-up for discussion.