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

Hearing withdraw routing logic #14129

Closed
2 tasks
chandracarney opened this issue Apr 28, 2020 · 0 comments · Fixed by #14278
Closed
2 tasks

Hearing withdraw routing logic #14129

chandracarney opened this issue Apr 28, 2020 · 0 comments · Fixed by #14278
Labels
Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-hearings Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Tango 💃 Type: Bug

Comments

@chandracarney
Copy link

chandracarney commented Apr 28, 2020

Description

For Legacy appeals with powers of attorney (POAs) that are private attorneys/agents and state/regional organizations, route the appeal to VACOLS location 81 (Case Storage) after the hearing request is withdrawn.

Currently cases with private attorney POAs are sent to VACOLS location 55 when they should have been sent to 81, which causes the case to be sent to a queue for veteran service organization (VSO) to write an informal hearing proposal (IHP) for it. If the Veteran isn't represented by a VSO and they are sent to location 55 in VACOLS, the record sits there for a long time until someone pulls a "55 report" and sees that it's been sitting for X days.

This misrouting requires Hearing Coordinators to go through a long flow in VACOLS to reroute the cases and encourages some to not use the Caseflow tools available.

If the appeal is Legacy, assign it to:

  • 55 if the POA / representative type is a Co-located Veteran Service Organization (VSO)
  • 81 (Case Storage) if the POA / representative type is any other, including:
    • private agent / attorney
    • state or regional VA organization (e.g. NC Department of Military & Veterans Affairs)
    • no representative
    • a non-co-located Veteran Service Organization (VSO)
  • If the appeal is AMA, assign it to Mail (create an EvidenceSubmissionWindow task, which is part of the Mail org)

Acceptance criteria

  • Correct routing to location 81

Background/context/resources

According to Caseflow documentation, this routing should already be happening:
https://github.com/department-of-veterans-affairs/appeals-team/blob/master/Project%20Folders/Caseflow%20Projects/Hearings/Hearing%20Schedule/Tech%20Specs/HearingTaskFlow.md#task-hierarchy

Legacy Appeal Flow:

  • Withdrawn Hearing Request (No Hearing Scheduled) Flow - The user cancels the ScheduleHearingTask, the Hearing task is automatically closed, and we move the appeal to location 81 (case storage) or 55 (if VSO or co-located)
  • Canceled Hearing Flow - We close the DispositionTask, the HearingTask is automatically closed, and we move the appeal to location 81 (case storage) or 55 (if VSO or co-located)

AMA Appeal Flow:

  • Withdrawn Hearing Request (No Hearing Scheduled) Flow - The user cancels the ScheduleHearingTask and the HearingTask is automatically closed"
  • Canceled Hearing Flow - We cancel the DispositionTask and the HearingTask is automatically closed

Technical notes

  • POA hash
  • Line 97 in the ScheduleHearingTask model
  • Possibility to reverse logic

Open questions

  • Can we tell the difference between VSO and state/regional VA or state or regional VA organization?
  • BGS has the distinction but when pulling it into Caseflow, we don't have that level of granularity.

Related tickets (routing)

@chandracarney chandracarney added Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-hearings Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Tango 💃 labels Apr 28, 2020
@chandracarney chandracarney removed this from the PI4-S2: Amelia Earhart Sprint milestone Jun 9, 2020
va-bot pushed a commit that referenced this issue Nov 3, 2020
Resolves #14129 
Resolves #14297 

### Description
Reverses the check of empty representatives to check whether the representative is part of a Vso and route to service organization location

### Acceptance Criteria
- [x] Code compiles correctly
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-hearings Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Tango 💃 Type: Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant