Linking Continued Trial Sessions

cholly75 commented 3 months ago

As a Court, so that we can accurately report out on the lifecycle of a particular case, we need to be able to indicate that a Special trial session is a continuance of a prior Special trial session.

Special trial sessions are often scheduled when a particular case or group of cases is complex enough to warrant its own trial session. Due to the nature of these cases, many times a single trial session is not enough to adjudicate the issues at hand, and the assigned judge will need to order more trial sessions in the future for the same case(s).

Currently each trial session exists as its own entity, with its own data and its own Session Copy for the assigned judge/CA/trial clerk. In order to establish connective tissue between these continuances to allow for more accurate reporting and recordkeeping, we would like to implement the following options w/r/t scheduling a Special trial session.

Pre-Conditions

Acceptance Criteria

When creating or editing a Special trial session, the user can indicate that this session is a Continuance of a previously scheduled Special trial session
When the user indicates that this Special trial session is a Continuance, they are required to select a previously scheduled Special trial session that is being continued
- Ideally the user is presented with a pre-filtered list of the selected judge's previously scheduled Special trial sessions to associate with the current trial session
- Upon saving the Special trial session as a Continuance, the previously scheduled Special trial session being continued indicates that it has been continued, with the date/location/assigned judge of the continuance.

Notes

Tasks

Test Cases

Story Definition of Ready (updated on 12/23/22)

The following criteria must be met in order for the user story to be picked up by the Flexion development team. The user story must:

[ ] Is framed in business/user need, the value has been addressed.
[ ] Includes acceptance criteria
[ ] Has been refined
[ ] Pre conditions have been satisfied.

Process: Flexion developers and designers will test if the story meets acceptance criteria and test cases in Flexion dev and staging environments (“standard testing”). If additional acceptance criteria or testing scenarios are discovered while the story is in progress, a new story should be created, added to the backlog and prioritized by the product owner.

Definition of Done (Updated 5-19-22)

Product Owner

[ ] Acceptance criteria have been met and validated on the Court's migration environment
[ ] Add scenario to testing document, if applicable (https://docs.google.com/spreadsheets/d/1FUHKC_YrT-PosaWD5gRVmsDzI1HS_U-8CyMIb-qX9EA/edit?usp=sharing)

UX

[ ] Business test scenarios have been refined to meet all acceptance criteria
[ ] Usability has been validated
[ ] Wiki has been updated (if applicable)
[ ] Story has been tested on a mobile device (for external users only)

Engineering

[ ] Automated test scripts have been written, including visual tests for newly added PDFs.
[ ] Field level and page level validation errors (front-end and server-side) integrated and functioning.
[ ] Verify that language for docket record for internal users and external users is identical.
[ ] New screens have been added to pa11y scripts.
[ ] All new functionality verified to work with keyboard and macOS voiceover https://www.apple.com/voiceover/info/guide/_1124.html.
[ ] READMEs, other appropriate docs, and swagger/APIs fully updated.
[ ] UI should be touch optimized and responsive for external only (functions on supported mobile devices and optimized for screen sizes as required).
[ ] Interactors should validate entities before calling persistence methods.
[ ] Code refactored for clarity and to remove any known technical debt.
[ ] If new docket entries have been added as seed data to efcms-local.json, 3 local s3 files corresponding to that docketEntryId have been added to web-api/storage/fixtures/s3/noop-documents-local-us-east-1
[ ] Acceptance criteria for the story has been met.
[ ] If there are special instructions in order to deploy into the next environment, add them as a comment in the story.
[ ] If the work completed for the story requires a reindex without a migration, or any other special deploy steps, apply these changes to the following flexion branches:
- [ ] experimental1
- [ ] experimental2
- [ ] experimental3
- [ ] experimental4
- [ ] experimental5
- [ ] experimental6
- [ ] develop
[ ] Reviewed by UX on a deployed environment.
[ ] Reviewed by PO on a deployed environment. Can be deployed to the Court's test environment if prod-like data is required. Otherwise deployed to any experimental environment.
[ ] Deployed to the Court's staging environment.

katiecissell commented 3 months ago

Pre-refinement questions:

do we need to link this is anyway other than visual? Like if you do something to one special it in someway carries over to it? Treat it like the same entity?
Are there any reports that we should indicate the continuance 'label' on?
How does the judge tell the calendaring folks the trial is continued? Via an order? And then they'll go add/edit the session?
Do the petitioner's need to know this is a continuance? Or is it obvious since they were there for the first trial...
Have there been swing sessions that were continued and vice versa?

swongCO commented 2 months ago

UX Notes Figma file.

For special sessions:

[ ] Add a checkbox for linked session under Swing session checkbox
[ ] When the checkbox is selected, display a dropdown component that lists all sessions defined in the AC

On the Session Info page of the original session:

[ ] display the linked session info in the details card
[ ] the link will open the session info page of the linked session in a new tab

On the Session Info page of the linked session:

[ ] display the previous session info in the details card
[ ] the link will open the session info page of the previous session in a new tab

flexion / ef-cms