-
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
Case movement | Expediting cases to a judge for decision #11397
Comments
How many scenarios do we account for in the initial release? |
Do we set overarching rules for special case movement that automatically when a "special case movement task" (as in step #3) is created that all transcription related tasks be unblocked? |
User story: As a user I need the ability to first acknowledge specific hearing related tasks and then have the ability to bypass and override them so that I can move a case to a judge quickly |
Would this qualify as a scenario for special case movement? "Can someone cancel the attorney draft task on this case. Put it back in the VLJs 'assign' queue. The case has some issues with 'issues' and shouldn't be assigned to any attorney at the moment while the board figures stuff out." created a new JudgeAssignTask Would this or any previous workarounds created qualify as special case movement?? |
I wouldn't qualify that as special case movement, personally. I think that could just be a new action available to a VLJ on their cases (pull back / cancel assignment to attorney) |
Scenarios for special case movement: |
@stwards11 aren't those AOD scenarios? |
@lomky: Upon further research you are correct. |
Scenario: A veteran has a hearing scheduled and has not waived the 90 day evidence window and is currently in day 35. A judge requests to have this case pulled for review immediately. 1). A judge would need to enable "special case movement" |
Can expediting cases/special case movement be defined as: A specific user or set of users that are granted rights to bypass, cancel, or withdraw specific hearing related functions for hearing docket cases, that aren’t already ready for distribution to a judge, to be distributed? |
@stwards11 - based on our brief convo the other day, I agree that administratively acting on behalf of other users could be split out into another effort. Here's the ticket I created: #11801 |
Yes |
User scenarios to be considered: Scenario # 1 - A hearing has been held and the evidence window is open |
Reviewed phase 4 - expediting hearing cases - with Carolyn today. next steps:
Paper prototypes until Shawn gets Mural access |
Generally speaking yes, @laurjpeterson. Specifically, that checkbox will prevent the creation of the Evidence Window task altogether. The Transcription task is created regardless, though, which still blocks distribution. |
@hschallhorn It appears that all work on this epic is complete. Can you confirm? If yes, can/should this epic be closed and a new epic started when we hear back from JW and JG at BVA? |
Phase 4 and 5 are not complete, they need to have tickets written and prioritized/worked. We do know that JW specifically said they wanted Phase 4. The phase 5 here is "Phase 7" in the Case Movement Enhancements deck |
Note, phases 4 & 5 combined for implementation. |
Context
Caseflow built critical functionality for AMA cases to be processed in time for the law’s implementation. The team focused on the most straightforward path (also known as the happy path) an appeal could take to meet this deadline, and get to a “minimum viable” state.
Caseflow is now iterating on this initial feature set to handle other paths an appeal could take.
Goals for this functionality:
Strategy:
Proposed agile implementation:
Phase 1: Identify Gaps
Phase 2: Allow judges to reassign their AMA tasks
Phase 3: Distribute a case ready for distribution, that has no child tasks
Phase 4: Expedite hearing docket cases
Scenarios involved
Phase 5: Distribute cases with blocking child tasks
or reassigned to appropriate teams(Per John G. & Mike S. all blocking tasks should be cancelled)Scenarios involved
The text was updated successfully, but these errors were encountered: