Hearing withdraw routing logic #14129
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
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:
Acceptance criteria
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:
AMA Appeal Flow:
Technical notes
Open questions
Related tickets (routing)
The text was updated successfully, but these errors were encountered: