change EvidenceSubmissionWindowTasks expiration when hearing tasks are cancelled on an appeal with no hearing #14077
Labels
Priority: High
Escalations from Support, blocking issue/NO workaround, or "first in" priority for new work.
Product: caseflow-hearings
Stakeholder: BVA
Functionality associated with the Board of Veterans' Appeals workflows/feature requests
Team: Tango 💃
Milestone
Description
When a
ScheduleHearingTask
is cancelled (when the hearing is withdrawn), we automatically create anEvidenceSubmissionWindowTask
.Current behavior
If there’s a hearing associated with the appeal, the
EvidenceSubmissionWindowTask
will expire 90 days after the day the hearing was scheduled. If there’s no hearing, it will expire 90 days after the appeal’s receipt date. In a case where a hearing was never scheduled, this can cause theEvidenceSubmissionWindowTask
to expire the same day it was created, because its appeal's receipt date is more than 90 days in the past.Desired behavior
The
EvidenceSubmissionWindowTask
should expire 90 days after the hearing was withdrawn (when theScheduleHearingTask
was cancelled) on an appeal in the Hearing docket. AnEvidenceSubmissionWindowTask
on an appeal in the Hearing docket should never use the appeal's receipt date to calculate its expiration.An
EvidenceSubmissionWindowTask
on an appeal in the Evidence Submission docket should continue to use the appeal's receipt date to calculate its expiration.Acceptance criteria
Background/context/resources
Direction from the board and relevant regulations are cited in this slack thread.
The current behavior was originally implemented in February 2019 with PR #9340; the requirements were described in issue #7916.
The text was updated successfully, but these errors were encountered: