As an org admin or area lead reviewing invoices, I need to be able to easily identify when a VS exceeds 12 hours of transport time and or 16 hours total work time in a 24 hour period #239
Is your feature request related to a problem? Please describe.
As per CSSAT's contract with DCYF, the two business needs described in this problem statement represent process they ultimately want Sprout to facilitate.
Describe the solution you'd like
An easy way to identify when either of these two scenarios (or both) may be happening in visit reports submitted by a visit supervisor. While we haven't had conversation with provider org admins or area leads about the details or more specific requirements of this desired functionality, on the surface it sounds like a tally or counter that tracks individual visit supervisors's transport time and visit time, separately, and displays this somewhere (in the Summary view after reports are in Submitted status?) that org admins and area leads can see. How and where those two users groups would see the information, whether there needs to be any kind of flagging or warning, may differ (would the invoice file be a better place to see a roll up for area leads?), so before there might be a decision to commit resources to this work, analysis and requirements clarification are needed.
Describe alternatives you've considered
N/A
Additional context
As per discussion in Slack on 7/23/24 though: it would "not be easy..." as the solution would have to "cut across multiple visits" and the use case is unclear as is when/where/how to alert the user. Would we need to build a whole new tool for the leads? Sarah suggested we add this to the backlog for retention, since it is referenced in our contract and would be a helpful enhancement, however no prioritization is requested for this work as it seems especially complex/a heavy lift
Prioritization Process
[ ] Confirm the issue is a feature to which we want to devote resources.
[ ] 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. As per CSSAT's contract with DCYF, the two business needs described in this problem statement represent process they ultimately want Sprout to facilitate.
Describe the solution you'd like An easy way to identify when either of these two scenarios (or both) may be happening in visit reports submitted by a visit supervisor. While we haven't had conversation with provider org admins or area leads about the details or more specific requirements of this desired functionality, on the surface it sounds like a tally or counter that tracks individual visit supervisors's transport time and visit time, separately, and displays this somewhere (in the Summary view after reports are in Submitted status?) that org admins and area leads can see. How and where those two users groups would see the information, whether there needs to be any kind of flagging or warning, may differ (would the invoice file be a better place to see a roll up for area leads?), so before there might be a decision to commit resources to this work, analysis and requirements clarification are needed.
Describe alternatives you've considered N/A
Additional context As per discussion in Slack on 7/23/24 though: it would "not be easy..." as the solution would have to "cut across multiple visits" and the use case is unclear as is when/where/how to alert the user. Would we need to build a whole new tool for the leads? Sarah suggested we add this to the backlog for retention, since it is referenced in our contract and would be a helpful enhancement, however no prioritization is requested for this work as it seems especially complex/a heavy lift
Prioritization Process
[ ] Confirm the issue is a feature to which we want to devote resources.
[ ] 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.