Is your feature request related to a problem? Please describe.
The current process of catching and justifying invoicing exceptions (via the pink boxes) is cumbersome, confusing, and fragile; it leads to errors and rework. As a user, I want to be able enter pink box information and explain exceptions directly into Sprout, before submitting an invoice so that we do not have to go back and forth and the process is less prone to rework and errors.
Describe the solution you'd like
Revise Sprout UI to display warning/error messages and open text entry field for explanations when the following thresholds are reached:
(>=100 wait time minutes will require an explanation to be entered in Sprout UI.)
(>=600 miles distance will require an explanation in Sprout UI.)
(>75 miles for first leg of travel will require explanation in Sprout UI.)
(>=480 visit time minutes will require an explanation in Sprout UI.)
(>=480 drive time minutes will require an explanation in Sprout UI.)
(>$20 for reimbursable travel expenses will be flagged for explanation/revision.)
REQUIREMENT: Pink box explanation reasons are required for the provider to approve the report.
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.
[x] Label story as an active backlog issue (i.e. an issue on which we will be actively working).
[x] Prioritize the story relative to other items in the active backlog.
[x] Review progress/priorities in weekly collaboration meeting.
Is your feature request related to a problem? Please describe. The current process of catching and justifying invoicing exceptions (via the pink boxes) is cumbersome, confusing, and fragile; it leads to errors and rework. As a user, I want to be able enter pink box information and explain exceptions directly into Sprout, before submitting an invoice so that we do not have to go back and forth and the process is less prone to rework and errors.
Describe the solution you'd like Revise Sprout UI to display warning/error messages and open text entry field for explanations when the following thresholds are reached:
REQUIREMENT: Pink box explanation reasons are required for the provider to approve the report.
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.
[x] Label story as an active backlog issue (i.e. an issue on which we will be actively working).
[x] Prioritize the story relative to other items in the active backlog.
[x] Review progress/priorities in weekly collaboration meeting.