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

change EvidenceSubmissionWindowTasks expiration when hearing tasks are cancelled on an appeal with no hearing #14077

Closed
1 task done
tomas-nava opened this issue Apr 23, 2020 · 0 comments · Fixed by #14135
Closed
1 task done
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 💃

Comments

@tomas-nava
Copy link
Contributor

tomas-nava commented Apr 23, 2020

Description

When a ScheduleHearingTask is cancelled (when the hearing is withdrawn), we automatically create an EvidenceSubmissionWindowTask.

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 the EvidenceSubmissionWindowTask 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 the ScheduleHearingTask was cancelled) on an appeal in the Hearing docket. An EvidenceSubmissionWindowTask 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

  • good test coverage

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.

@tomas-nava tomas-nava added Team: Tango 💃 Product: caseflow-hearings Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Priority: High Escalations from Support, blocking issue/NO workaround, or "first in" priority for new work. labels Apr 23, 2020
va-bot pushed a commit that referenced this issue May 8, 2020
…ithdrawal date (#14135)

Resolves #14077 

### Description
Changed the logic for calculating when an EvidencesSubmissionWindow task expires. 
- Previously the expiration was based on receipt date so long as there was not an associated hearing.
- Now the task expires based on the receipt date only if in the evidence submission docket and it expires based on the hearing withdrawal date for all others

### Acceptance Criteria
- [ ] Code compiles correctly
- [ ] EvidenceSubmissionWindow task is closed at the correct time based on the docket and whether it has an associated hearing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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 💃
Projects
None yet
2 participants