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

Understand any Caseflow constraints for creating new hearing day without a room associated #14614

Closed
1 of 2 tasks
chandracarney opened this issue Jun 29, 2020 · 3 comments
Closed
1 of 2 tasks
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 💃

Comments

@chandracarney
Copy link

chandracarney commented Jun 29, 2020

Description

Investigate and understand if Caseflow adds constraints around building new (single) hearing days. Hearing Coordinator admins have the ability to add one-off hearing days, however, they have reported that they cannot add a new day and assign a new VLJ because:

  • VLJs cannot be assigned to a docket unless a room is added
  • All rooms are taken and a room cannot be double-booked
  • Veterans cannot be added to rooms

Caseflow might need to 1) allow hearing day to be assigned a VLJ even if a room is not assigned, or 2) allow rooms to be double-booked.

Acceptance criteria

  • Document any constraints
  • TBD: Write a new ticket to remove constraints

Background/context/resources

As a Hearing Coordinator admin with schedule building capabilities, I need to be able to create an additional hearing day without a hearing room assignment, so that additional VLJs (outside the normal schedule) assigned to virtual and/or AMA-only cases can hold hearings.

After 3 months of postponements through the pandemic, the Board would like to boost hearing capacity by scheduling more virtual hearings to alleviate built up hearing inventory. Because AMA cases can be heard and decided by different VLJs (vs. Legacy which must be heard and decided by the same VLJ), building AMA-only dockets will allow the Board to start alleviating the inventory.

Considerations

  • Our end goal will be to have constraints for video/Central dockets to be associated with hearing rooms when we introduce fully virtual dockets.

Technical notes

@chandracarney chandracarney added 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 💃 labels Jun 29, 2020
@chandracarney chandracarney reopened this Jun 29, 2020
@ferristseng
Copy link
Contributor

ferristseng commented Jul 8, 2020

Constraints in Caseflow

I went through to confirm whether or not these constraints were enforced by Caseflow, and noticed that most of these things are possible, but not supported well in the UI. I noted some things in the UI that might be confusing in the 2nd section, but we might want to talk to some hearing coordinators to get further details about the limitations they are running into.

❌ = not a constraint
🧐 = kind of a constraint

Constraint Verified Comment
VLJs cannot be assigned to a docket unless a room is added I was able to assign a VLJ to a day without a room both when I was adding the new day, and editing it Screen Shot 2020-07-08 at 11 48 11 AM
All rooms are taken and a room cannot be double-booked 🧐 When you're adding a new hearing day, you don't have the option to double-book a room (create an identical hearing day), but you are able to edit an existing hearing day and assign it to the same room as another hearing day. This is a workaround, but it's not disallowed by any existing constraints in Caseflow Screen Shot 2020-07-08 at 12 00 34 PM
Veterans cannot be added to rooms 🧐 I think the UI is confusing around if there are multiple rooms on the same day, but from what I could tell, Caseflow does not enforce any constraint that would prevent a veteran to be added to a room

Issues in Caseflow

I noted some issues that make working with multiple dockets on the same day very confusing:

Issue Screenshot
When scheduling a veteran, there is no way to distinguish multiple dockets on the same day from one another. This makes it difficult to select the intended hearing day. We could supply the room or VLJ here to clarify the HC's selection Screen Shot 2020-07-08 at 11 40 14 AM
On the schedule veteran's screen, selecting a duplicate/double-booked docket highlights multiple entries on the sidebar. The room displays as null, and there is no way to distinguish multiple dockets on the same day from each other. Screen Shot 2020-07-08 at 11 41 12 AM

Comments

Caseflow might need to 1) allow hearing day to be assigned a VLJ even if a room is not assigned, or 2) allow rooms to be double-booked.

I think both of these are currently enabled by Caseflow. For 2, there is a work-around to double-book rooms, but we should probably support it directly in the add hearing day modal (right now the room is automatically selected or can be left blank, but there is no way to select a room directly unless you go to the edit screen).

As a Hearing Coordinator admin with schedule building capabilities, I need to be able to create an additional hearing day without a hearing room assignment, so that additional VLJs (outside the normal schedule) assigned to virtual and/or AMA-only cases can hold hearings.

Were the HC's thinking of leveraging the notes field to indicate that a docket should be virtual/AMA-only (since we don't have any way of marking that in Caseflow right now)? We would need to modify some of the UI to display those notes so they have that information while selecting a hearing date and time.

@ferristseng
Copy link
Contributor

Closing in favor of the issues that came out of this

@chandracarney
Copy link
Author

Issues created from this work: #14671, #14673, #14674

va-bot pushed a commit that referenced this issue Jul 13, 2020
### Description

  * Organizing imports
  * Make functional components
  * Removing unused code

### Storybook Story

Unsure if these components will change in the near future, so I'm going to hold off on any storybook story or jest tests for now. I think for the tickets that come out of #14614, we can be more thorough in addressing tech debt/refactoring
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 💃
Projects
None yet
Development

No branches or pull requests

2 participants