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

Display virtual hearing guest link to Hearing Coordinators #13936

Closed
nicholer opened this issue Apr 9, 2020 · 2 comments · Fixed by #14118
Closed

Display virtual hearing guest link to Hearing Coordinators #13936

nicholer opened this issue Apr 9, 2020 · 2 comments · Fixed by #14118
Assignees
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 💃 Type: design 💅 Used by the design team to keep track of design work that may need design review before shipping

Comments

@nicholer
Copy link

nicholer commented Apr 9, 2020

User story

As a Hearing Coordinator, I want to be able to see (and access) the virtual hearing guest link in Caseflow UI so that I can better assist Veterans and POAs who are experiencing difficulties joining their hearing link.

Background/context

Currently Hearing Coordinators only have access to the host virtual hearing link (aka VLJ link) and are experiencing difficulty troubleshooting hearing connection issues with Veterans and POAs without access to the guest link. In the event of an email issue, Hearing Coordinators may need access to the guest link so that they may resend the link to a Veteran and/or POA.

Displaying the guest link in the Caseflow UI on Hearing Details is preferred to creating a new email to send to Hearing Coordinators because (1) updating the Caseflow UI is a lower technical lift and (2) the Coordinator who creates a virtual hearing may not be the one who actually conducts testing and facilitates the hearing.

While the Board intends on moving away from Hearing Coordinators testing the connection with participants in a high-touch way, virtual hearings have rolled out at a higher volume than originally planned due to the COVID-19 pandemic, delaying the move towards a more low-touch method.

Design

https://www.figma.com/file/V87TZArfdurCGJiEjQ73ES/Virtual-Hearings?node-id=435%3A801

Acceptance criteria

  • On Hearing Details, the Virtual Hearing Details section displays the VLJ Link and the Guest Link
  • When the async job to create the Pexip videoconference is in-progress:
    • The VLJ Link field label displays; the value is placeholder text Scheduling in progress
    • The Guest Link field label displays; the value is placeholder text Scheduling in progress
  • After the Pexip videoconference is created:
    • The following VLJ Link information displays:
      • VLJ Link: field label
        • value is Open Virtual Hearing, which is formatted as a link; clicking the link opens the videoconference in a new tab
      • Conference Room: field label
        • value is conference room alias, formatted as text BVA#####@care.va.gov
      • PIN: field label
        • value is host PIN, formatted as text
      • Copy VLJ Link button; on-click, the full host URL is copied to the user's clipboard
    • The following Guest Link information displays:
      • Guest Link: field label
        • value is Open Virtual Hearing, which is formatted as a link; clicking the link opens the videoconference in a new tab
      • Conference Room: field label
        • value is conference room alias, formatted as text BVA#####@care.va.gov
      • PIN: field label
        • value is guest PIN, formatted as text
      • Copy Guest Link button; on-click, the full guest URL is copied to the user's clipboard
  • After the hearing day (i.e. when the videoconference is cleaned up):
    • The following link information displays:
      • VLJ Link: and Guest Link: values are Expired, formatted as text
      • the copy link buttons don't display
@nicholer nicholer added Priority: High Escalations from Support, blocking issue/NO workaround, or "first in" priority for new work. Product: caseflow-hearings Team: Tango 💃 Type: design 💅 Used by the design team to keep track of design work that may need design review before shipping labels Apr 9, 2020
@nicholer nicholer self-assigned this Apr 9, 2020
@nicholer nicholer added the Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests label Apr 10, 2020
@nicholer
Copy link
Author

nicholer commented Apr 13, 2020

Context from @carodew in another ticket:

Would like to add some context – the copy to clipboard pattern that we've used elsewhere in Caseflow has had some accessibility issues that we've corrected on a one-off basis. Asking to make sure that the implementation in this case includes the fixes we've incorporated (I know @chandracarney will be able to provide guidance on this front).

@nicholer
Copy link
Author

nicholer commented Apr 23, 2020

Next steps 4/23 based on Coordinator feedback

  • Label judge link "VLJ Link"
  • Label conference "Conference Room"
  • The Conference Room value format = conference room alias ([email protected])
  • Design in-progress state
  • Finalize ticket requirements
  • [Optional] [Explore quick help text about who the VLJ Link and Guest Link are for? This may help mitigate the visual association between Guest Link and POA]

va-bot pushed a commit that referenced this issue May 1, 2020
Resolves #13936 

### Description
Updated Hearing Details UI based on figma diagram: https://www.figma.com/file/V87TZArfdurCGJiEjQ73ES/Virtual-Hearings?node-id=425%3A15036

### Acceptance Criteria
- [ ] Code compiles correctly
- [ ] User sees "Scheduling in progress" when conference is being created and emails generated
- [ ] User sees virtual hearing details and a button to copy both guest and host link when the virtual hearing has been scheduled
- [ ] User sees expired when the virtual hearing is past or if it is cancelled

### Testing Plan
1. Select judge "BVAYELLOW": http://localhost:3000/test/users
1. Navigate to hearings:  http://localhost:3000/hearings/schedule
1. Choose a "Video" hearing
1. Click the "Edit hearing details" link
1. Ensure you do not see any virtual hearing details
1. Change from a "Video" hearing to a "Virtual" hearing and ensure you see the "Scheduling in progress" label
1. Once the virtual hearing has been scheduled, confirm that you see details for both the host and guest based on the Figma diagram above.
1. Change the hearing back to "Video" and ensure that you see the expired status based on the Figma diagram

### User Facing Changes

 BEFORE|AFTER
 ---|---
*Previous Virtual Hearing*
![BeforeHearingLinkPrevious](https://user-images.githubusercontent.com/61989526/80509413-6184d500-8947-11ea-85c2-40d8ad5e5b7b.png)|![AfterHearingLinkPrevious](https://user-images.githubusercontent.com/61989526/80509648-b32d5f80-8947-11ea-885b-86248d2a70e6.png)
*Virtual Hearing in progress*
![BeforeHearingLinkInProgress](https://user-images.githubusercontent.com/61989526/80509412-6184d500-8947-11ea-87f4-f86f947d11ec.png)|![AfterHearingLinkInProgress](https://user-images.githubusercontent.com/61989526/80727098-4b0b8480-8ad3-11ea-8c3d-2f1d00cddfa4.png)
*Virtual Hearing Active*
![BeforeHearingLinkActive](https://user-images.githubusercontent.com/61989526/80727006-2a432f00-8ad3-11ea-9688-0535cc7ded85.png)|![AfterHearingLinkActive](https://user-images.githubusercontent.com/61989526/80726930-0ed82400-8ad3-11ea-8c9b-9d6303da6ff3.png)
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 💃 Type: design 💅 Used by the design team to keep track of design work that may need design review before shipping
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants