| Tasks Overview | All Tasks | DR tasks | ES tasks | H tasks |
NoShowHearingTask_Organization Description #
Task stats for DR, for ES, for H dockets.
- Task created after an appellant no-shows for a hearing. Gives the hearings team the options to decide how to handle the no-show hearing after the judge indicates that the appellant no-showed.
See HearingTask for Hearing dispositions flows, esp. the “No show” flow.
Code comments extracted from Ruby file:
-
Task created after an appellant no-shows for a hearing. Gives the hearings team the options to decide how to handle the no-show hearing after the judge indicates that the appellant no-showed.
-
Task is created as a child of AssignHearingDispositionTask with a TimedHoldTask which is set to expire after
-
DAYS_ON_HOLD days. Before the task expires, users can manually complete this task, postpone hearing, or create a
-
ChangeHearingDispositionTask.
-
If DAYS_ON_HOLD as passed, TaskTimerJob cleans up the TimedHoldTask and automatically completes NoShowHearingTask.
-
Completion/cancellation of NoShowHearingTaskcan trigger closing of parent AssignHearingDispositionTask and if AssignHearingDispositionTask was the last open task of grandparent HearingTask, either of the following can happen:
- If appeal is AMA, create an EvidenceSubmissionWindowTask as child of HearingTask OR
- If appeal is Legacy, route location according to logic in HearingTask#update_legacy_appeal_location