department-of-veterans-affairs / caseflow

Caseflow is a web application that enables the tracking and processing of appealed claims at the Board of Veterans' Appeals.
Other
53 stars 18 forks source link

Intake | Docket Change | Prototype 3 #15075

Closed rutvigupta-design closed 4 years ago

rutvigupta-design commented 4 years ago

User story and requirements

As an Attorney with the Office of the Clerk of the Board, I want to be able to change the docket type for a claimant's appeal to/from (1. Direct Review, 2. Evidence submission, 3. Hearing Request) for a granted Request to Modify in order to move the claimant's appeal to the requested docket and initiate subsequent tasks.

Acceptance criteria

Out of scope

Designs beyond the indicated user story

Background/context

Please see the Mural for the end-to-end user workflow. Please see the epic for more background.

Resources/other links

Epic Mural with user workflow

rutvigupta-design commented 4 years ago

Open questions/Considerations:

  1. We'll need to figure out what the Case Timeline looks like for the new appeal stream — what should the behavior would be here? (JC's guess is there would simply be the new/moved tasks w/o indication of docket switch)
  2. We should confirm that users don't need to create a Dispatch task in order to send notification to claimant that the docket switch has been completed
  3. Need to define the scope of the VLJ/Clerk's decision within/outside of Caseflow
  4. Need to clarify that this flow will work if it's initiated by an attorney/VLJ/hearing coordinator down the line
  5. Need to re-confirm that stories for a VLJ/attorney sending an identified docket switch request is out of scope
  6. How will we handle detail rotations and permissions? - Resolved by eng; Slack thread here
  7. Re-confirm that for partial grants, tasks should still transferred over and there should still only be one of the tasks? Does it matter which docket the tasks are associated with?