Skip to content
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

Automatically place CAVC Remands without mandate on hold #14773

Closed
8 tasks
araposo-tistatech opened this issue Jul 27, 2020 · 0 comments
Closed
8 tasks

Automatically place CAVC Remands without mandate on hold #14773

araposo-tistatech opened this issue Jul 27, 2020 · 0 comments
Labels
Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-queue Team: Echo 🐬 Type: New Development New feature development

Comments

@araposo-tistatech
Copy link

araposo-tistatech commented Jul 27, 2020

User or job story

User story: As a CAVC Litigation Support user, I need a new task type to be created for MDR CAVC Remands, so that the task can be placed on hold until I need to continue processing the case.

Acceptance criteria

  • This feature should be accessible to the following user groups: CAVC Litigation Support
  • Include screenshot(s) in the Github issue if there are front-end changes
  • Update documentation: CAVC Remand
  • Verify new task type MDR Task is created
  • Verify the task is assigned to the CAVC Litigation Support team
  • Verify the task is child of CAVC task on new appeal stream
  • Verify the task is automatically placed on hold for 90 days
  • Verify the following actions are available on the task:
    • Remand Ready for 90 Day Letter - sends user to form to complete intake
    • Put task on hold - presents on hold modal

Designs

MDR

Technical notes

The functionality to place tasks on hold for litigation support users already exists. This will just automate the process so that when they create an MDR CAVC Remand they do not have to go back to the task just to place it on hold.
How we do this in caseflow!

  1. For no show hearing tasks - Create a timed hold task immediately after create
  2. For evidence submission window tasks - Created as a timeable task which automatically closes when the hold is completed

Think we want to go with the no show hearing implementation as we want the task to be actionable after the hold is completed and want the user to be able to end the hold early which is already implemented for task with timed hold task children

Other notes

Resources/other links

@araposo-tistatech araposo-tistatech added Product: caseflow-queue Team: Echo 🐬 Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Type: New Development New feature development labels Jul 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-queue Team: Echo 🐬 Type: New Development New feature development
Projects
None yet
Development

No branches or pull requests

1 participant