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

Allow Hearing Branch to change docket without cancelling or postponing #12653

Closed
3 tasks
pshahVA opened this issue Nov 8, 2019 · 2 comments
Closed
3 tasks
Assignees
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: content ✍🏽 Used by design team to track/filter issues that have content questions or implications. Type: design 💅 Used by the design team to keep track of design work that may need design review before shipping

Comments

@pshahVA
Copy link

pshahVA commented Nov 8, 2019

User story

As a hearings branch user I need to correct a docket without having to mark the appeal as cancelled, postponed, or withdrawn.

Background/context

When mistakes are made while scheduling hearings, there is no way to undo a mistake without canceling, postponing, or withdrawing a hearing.

  • A cancelation, postponement, or withdraw are recorded in the disposition, even though it is really a clerical error. Users might make notes "scheduled in error."
  • If it's the first time a Veteran has postponed their hearing, the hearing can be automatically rescheduled, they don't need a ruling. But If Coordinator postpones due to a scheduling error, that creates burden on the Hearing Coordinators to track if the Veteran is able to reschedule automatically.
  • False reporting metrics are being created: high numbers of postponed/cancelled hearings appear even though they are clerical errors.

Acceptance criteria

  • Please put this work behind the feature toggle: [hearings_edit]
  • This feature should be accessible to the following user groups: TBD
  • Include screenshot(s) in the Github issue if there are front-end changes TBD

Release notes

New type of action can be made on a scheduled hearing that doesn't require canceling, postponing, or withdrawing a hearing.

Out of scope

Designs

Technical notes

Create new action that cancels ScheduledHearingTask and doesn't update VACOLS

Resources/other links

This feels related to #12168 (Research: "Withdraw hearing" -> "Cancel hearing request" label change)

Open questions

  • Do we need to track the "undo/remove/revert" that Hearing Coordinators perform?
    • It will be tracked, but the new type wouldn't perform the VACOLS action(s). There would be a record.
@jimruggiero
Copy link

Moving to Define until baseline requirements are complete for Design and/or ENG.

@jimruggiero jimruggiero added Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Product: caseflow-hearings Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. labels Dec 29, 2019
@nicholer nicholer self-assigned this Apr 6, 2020
@nicholer nicholer changed the title Allow hearings branch to change docket without cancelling or postponing. Allow Hearing Branch to change docket without cancelling or postponing Apr 6, 2020
@nicholer nicholer added Type: content ✍🏽 Used by design team to track/filter issues that have content questions or implications. Type: design 💅 Used by the design team to keep track of design work that may need design review before shipping labels May 7, 2020
@chandracarney chandracarney changed the title Allow Hearing Branch to change docket without cancelling or postponing Allow Hearing Branch to change docket without cancelling, postponing, or withdrawing May 21, 2020
@chandracarney chandracarney changed the title Allow Hearing Branch to change docket without cancelling, postponing, or withdrawing Allow Hearing Branch to change docket without cancelling or postponing May 22, 2020
@lund5000
Copy link
Contributor

lund5000 commented Jun 2, 2021

Completed in https://vajira.max.gov/browse/CASEFLOW-132

@lund5000 lund5000 closed this as completed Jun 2, 2021
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: content ✍🏽 Used by design team to track/filter issues that have content questions or implications. Type: design 💅 Used by the design team to keep track of design work that may need design review before shipping
Projects
None yet
Development

No branches or pull requests

4 participants