Is your feature request related to a problem? Please describe.
Currently, Sprout does not know how to handle unsupervised overnight visits: when a worker drops a child off and leave the child for an unsupervised visit, overnight. Then someone (possibly a different person than one that dropped the child off) picks up the child on the next day/on another day and Sprout does not effectively allow users to enter information on this kind of scenario (and users have to find a work around, which means the data for these visits is flawed). Sprout also requires entering the visit start time instead of pick up time, which means people have to enter data incorrectly (since the time a child is picked up is not the same thing as when a visit begins).
As a user, I want to be able to accurately depict visit report information for unsupervised visits, including distinct child pick up and visit start time values so that I may be paid correctly without having to find a work around and so that visit data will be correct and of better quality for reporting.
Describe the solution you'd like
We need to study what a visit is in Sprout and consider modifying the concept of a visit so it is not constrained to 1 calendar day (we could have a visit start and end date for example).
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Prioritization Process
[X] Confirm the issue is a feature to which we want to devote resources.
[X] Write user story in as a (role) I want (something) so that (benefit) format.
[ ] Label story Large, Uncertain, Small. If the story is too large, convert the story to a milestone/epic.
[ ] Label story as an active backlog issue (i.e. an issue on which we will be actively working).
[ ] Prioritize the story relative to other items in the active backlog.
[ ] Review progress/priorities in weekly collaboration meeting.
Is your feature request related to a problem? Please describe. Currently, Sprout does not know how to handle unsupervised overnight visits: when a worker drops a child off and leave the child for an unsupervised visit, overnight. Then someone (possibly a different person than one that dropped the child off) picks up the child on the next day/on another day and Sprout does not effectively allow users to enter information on this kind of scenario (and users have to find a work around, which means the data for these visits is flawed). Sprout also requires entering the visit start time instead of pick up time, which means people have to enter data incorrectly (since the time a child is picked up is not the same thing as when a visit begins).
As a user, I want to be able to accurately depict visit report information for unsupervised visits, including distinct child pick up and visit start time values so that I may be paid correctly without having to find a work around and so that visit data will be correct and of better quality for reporting.
Describe the solution you'd like We need to study what a visit is in Sprout and consider modifying the concept of a visit so it is not constrained to 1 calendar day (we could have a visit start and end date for example).
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.
Prioritization Process
[X] Confirm the issue is a feature to which we want to devote resources.
[X] Write user story in
as a (role) I want (something) so that (benefit)format.[ ] Label story Large, Uncertain, Small. If the story is too large, convert the story to a milestone/epic.
[ ] Label story as an active backlog issue (i.e. an issue on which we will be actively working).
[ ] Prioritize the story relative to other items in the active backlog.
[ ] Review progress/priorities in weekly collaboration meeting.