-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dispatch Stats | Display stats charts #819
Comments
I think the notion should be that we need to cache any such fields in Caseflow. But as far as I see, there are only two: the type of decision and the outcoding date. Both are already being used in the app, just perhaps not being cached. |
There's an issue here. The logic assumes that there is not more than one task per appeal, but this is not necessarily the case. If a task expires (completion status of 2), it'll be recreated. |
To QA: Sharon is out on vacation, ping me if you find any issues |
As a system administrator I want to be able to see all the business stats about how people are using Caseflow Dispatch.
Acceptance Criteria
Tasks identified — task.created_at within the period, where this is the first task.created_at with a given task.appeal_id.
Full grant —We'd want to use appeal.full_grant? for this, but that's currently subject to a problem in that it uses the status of the case to determine. This works at the moment it is being dispatched, but after a remand is worked, it will be placed in HIS status and be marked as a full grant. We need to replace this method to instead use a count of the issues on the case. If the number of issues where ISSDC = '1' is greater than 0, but the number of issues where ISSDC = '3' is equal to zero, it's a full grant. Similarly, we can replace the partial and remand methods; if it has both 1s and 3s it's a partial, and if it has 3s but no 1s, it's a remand.
Active users — Uniqued
task.user_id
of those tasks wheretask.completed_at
is within the period. Note that this includes cancellations as well as successfully established claims.Tasks started —
task.started_at
within the period.Tasks completed —
task.completed_at
within the period wheretask.completion_status
is equal to "completed" (0).Completion rate — The percentage of tasks completed within the period (
task.completed_at
) wheretask.completion_status
is equal to "completed" (0).Time to claim establishment — The difference between the
FOLDER.TIOCTIME
time from VACOLS and thetask.completed_at
time in days for tasks completed within the period (task.completed_at
) wheretask.completion_status
is equal to "completed" (0).Cancellations —
task.completed_at
within the period wheretask.completion_status
is equal to "canceled" (1).Mockups
View - Stats - Certification Daily
Notes
The text was updated successfully, but these errors were encountered: