Status Order Report Enhancement - Prepopulate Docket Entry Fields

As a docket clerk, so that I do not need to assemble a docket entry description manually for status report orders, I need status report orders generated by DAWSON to prepopulate the docket entry description for me.

When the generated draft status report order is added to the docket record, docket clerks must scan the order and make adjustments to the document description and in some cases document type itself. Given that these edits are based entirely on text generated from selections made in the process of generating the order itself, we would like to use our knowledge of those selections to prepopulate the docket entry fields when docketing to reduce the amount of manual work and potential for error on the part of the docket clerk. This will also help ensure a uniform description for these types of orders.

The AC below should apply to all draft generated status report orders only. Examples of desired behavior in the Notes below.

Pre-Conditions

Acceptance Criteria

Default text in the "What is this order for?"/Description fields is prepopulated and assembled on the Add Docket Entry screen based on selections made in the OSR generator in two sections: Order Type and Jurisdiction.
Docket clerk can still edit any of the prepopulated fields/text as per usual.
ORDER TYPE:
- If "Status Report" is selected, then the text "Parties by [DATE] shall file a status report." is added to the description
- If "Status Report or Stipulated Decision" is selected, then the text "Parties by [DATE] shall file a status report or proposed stipulated decision." is added to the description.
- In both of the above cases, [DATE] represents the due date selected in the generator, in the format mm/dd/yy
- JURISDICTION:
- If "Case is stricken from the trial session" is checked, then the text "Case is stricken from the current trial session." is added to the description field.
  - If "Restored to general docket" is selected, then "Case is no longer jurisdiction retained and is restored to the general docket." is added to the description field.
  - If "Retained" is selected, then several things happen:
  - The document type is changed to "Order jurisdiction is retained" (OJR)
  - The Judge associated with the order is changed to be the signing judge if the order is signed
ASSEMBLING THE DESCRIPTION:
- If the document type is O then the "What is this order for?" field on the Add Docket Entry screen is prepopulated with:
- Order + Order Type section verbiage (note no capitalization on "parties" in this instance) + Jurisdiction section "stricken" verbiage + Jurisdiction section "Restored" verbiage
- If the document type is OJR then the "Description" field on the Add Docket Entry screen is prepopulated with:
- Order that jurisdiction is retained by Judge [JUDGE] +a period + Order Type section verbiage + Jurisdiction section "stricken" verbiage
- NOTE: OJR documents automatically append the description field text to the default text "Order that jurisdiction is retained by [JUDGE]" as shown in the Docket entry preview text on the screen. This behavior remains the same.

Notes

Example 1: Given the following selections used to generate a status report order:

The following is displayed on the Add Docket Entry screen:

Example 2: Given the following selections used to generate a status report order:

The following is displayed on the Add Docket Entry screen:

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)

[ ] 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.

Test Cases

1) Judge user creates a Status Order Report, selects "Status Report"; When Docket clerk adds the docket entry appropriate text is in the description.

Log in as a Judge
Navigate to a case that has a Status Report that has been filed on the case
Open the document
Click on the Order Report link
Select Status Report, and add in a date
Save the draft and add a signature
Send a message to a docket clerk and be sure that the Order Report is attached to the message
Log in as a docket clerk
Navigate to your message with the Status Report
Click on the Add Docket Entry link at the top of the document view

Expected Results:

[ ] NEW FUNCTIONALITY - The text in the "What is this Order for?" field is "Order parties by [DATE INPUT] shall file a status report."
[ ] Document type is Order
[ ] After clicking Served, clerk can click Save and Serve and the document is added to the docket record and served as per normal
[ ] NEW FUNCTIONALITY - The document description on the docket record is "Order parties by [DATE INPUT] shall file a status report."

*Repeat this test but instead click the Save Entry button. Be sure that you can navigate back to the document and serve as per normal.

2) Judge user creates a Status Order Report, selects "Status Report or Stipulated Decision"; When Docket clerk adds the docket entry appropriate text is in the description.

Log in as a Judge
Navigate to a case that has a Status Report that has been filed on the case
Open the document
Click on the Order Report link
Select Status Report or Stipulated Decision, and add in a date
Save the draft and add a signature
Send a message to a docket clerk and be sure that the Order Report is attached to the message
Log in as a docket clerk
Navigate to your message with the Status Report
Click on the Add Docket Entry link at the top of the document view

Expected Results:

[ ] NEW FUNCTIONALITY - The text in the "What is this Order for?" field is "Order parties by [DATE INPUT] shall file a status report or proposed stipulated decision."
[ ] Document type is Order
[ ] After clicking Served, clerk can click Save and Serve and the document is added to the docket record and served as per normal
[ ] NEW FUNCTIONALITY - The document description on the docket record is "Order parties by [DATE INPUT] shall file a status report or proposed stipulated decision."

*Repeat this test but instead click the Save Entry button. Be sure that you can navigate back to the document and serve as per normal.

3) Judge user creates a Status Order Report, selects "Status Report" and "Case is stricken from the trial session" and "Restored to the general docket"; When Docket clerk adds the docket entry appropriate text is in the description.

Log in as a Judge
Navigate to a case that has a Status Report that has been filed on the case
Open the document
Click on the Order Report link
Select Status Report, add in a date and also select the box for "Case is stricken from the trial session" and select "Restored to the general docket"
Save the draft and add a signature
Send a message to a docket clerk and be sure that the Order Report is attached to the message
Log in as a docket clerk
Navigate to your message with the Status Report
Click on the Add Docket Entry link at the top of the document view

Expected Results:

[ ] NEW FUNCTIONALITY - The text in the "What is this Order for?" field is "Order parties by [DATE INPUT] shall file a status report. Case is stricken from the current trial session. Case is no longer jurisdiction retained and is restored to the general docket."
[ ] Document type is Order
[ ] After clicking Served, clerk can click Save and Serve and the document is added to the docket record and served as per normal
[ ] NEW FUNCTIONALITY - The document description on the docket record is "Order parties by [DATE INPUT] shall file a status report. Case is stricken from the current trial session. Case is no longer jurisdiction retained and is restored to the general docket."

Repeat this test but instead click the Save Entry button. Be sure that you can navigate back to the document and serve as per normal. Repeat this test, but instead choose Status report or Stipulated Decision"

4) Judge user creates a Status Order Report, selects "Status Report" and "Case is stricken from the trial session" and "Retained"; When Docket clerk adds the docket entry appropriate text is in the description and the Document type is OJR.

Log in as a Judge
Navigate to a case that has a Status Report that has been filed on the case
Open the document
Click on the Order Report link
Select Status Report, add in a date and also select the box for "Case is stricken from the trial session" and select "Retained"
Save the draft and add a signature
Send a message to a docket clerk and be sure that the Order Report is attached to the message
Log in as a docket clerk
Navigate to your message with the Status Report
Click on the Add Docket Entry link at the top of the document view

Expected Results:

[ ] NEW FUNCTIONALITY - Document type is Order that jurisdiction is retained
[ ] There is a Judge's Name field. Judge's name is auto-populated with the judge's name that signed the Order
[ ] NEW FUNCTIONALITY - The text in the "Description" field is ". Parties by [DATE INPUT] shall file a status report. Case is stricken from the current trial session."
[ ] After clicking Served, clerk can click Save and Serve and the document is added to the docket record and served as per normal
[ ] NEW FUNCTIONALITY - The document description on the docket record is "Order that jurisdiction is retained by Judge [JUDGE NAME]. Parties by [DATE INPUT] shall file a status report. Case is stricken from the current trial session."

Repeat this test but instead click the Save Entry button. Be sure that you can navigate back to the document and serve as per normal. Repeat both tests above, but instead choose Status report or Stipulated Decision" *Repeat the test above, but as the Judge, don't sign the order and just send the message to Docket.

[ ] There is NOT any pre-populated Judge Name in the Judge Name field.
[ ] The docket clerk cannot add the docket entry w/o a signature (as per normal)

5) Judge user creates a Status Order Report, makes various selections and adds in Additional order text; When docket clerk adds the docket entry, the additional order text is not included in the description.

Log in as a Judge
Navigate to a case that has a Status Report that has been filed on the case
Open the document
Click on the Order Report link
Select Status Report, add in a date and also make various other selections as you would like.
Add in some Additional Order Text.
Save the draft and add a signature
Send a message to a docket clerk and be sure that the Order Report is attached to the message
Log in as a docket clerk
Navigate to your message with the Status Report
Click on the Add Docket Entry link at the top of the document view

Expected Results:

[ ] There is no additional order text displayed in the "What is this Order For?" field or in the "Description" field (if an OJR Order).

Repeat this test but instead click the Save Entry button. Be sure that you can navigate back to the document and serve as per normal. Repeat both tests above with various combinations of data entry in the Status Order Report. There shouldn't ever be any Additional Order Text present in the description fields.

6) Judge user creates a Status Report Order, makes various selections; When docket clerk adds the docket entry, the clerk can edit the generated Order type and the generated description.

Log in as a Judge
Navigate to a case that has a Status Report that has been filed on the case
Open the document
Click on the Order Report link
Select Status Report, add in a date and also make various other selections as you would like.
Save the draft and add a signature
Send a message to a docket clerk and be sure that the Order Report is attached to the message
Log in as a docket clerk
Navigate to your message with the Status Report
Click on the Add Docket Entry link at the top of the document view

Expected Results:

[ ] The Docket clerk can edit the auto-generated text in the "What is this Order For?" field or the Description field if OJR order was selected.
[ ] Docket clerk can edit the Order type
[ ] Docket clerk can edit the Judge name (if OJR order)
[ ] Docket clerk can save the edited fields as per normal
[ ] Docket entry display on the docket record displays whatever text was saved on the Add Docket Entry screen.

7) Repeat the tests above with a Status Order Report in the lead case of a consolidated group, and select All cases in the group.

Same steps as above, but when the docket clerk clicks on the Save and Serve button they will receive the Serve to all cases in the group modal.

Expected Results:

[ ] NEW FUNCTIONALITY - Each case's docket entry on the docket record displays the appropriate text as indicated in the test cases above (depending on the selections made)
- [ ] Test case 1
- [ ] Test case 2
- [ ] Test case 3
- [ ] Test case 4
- [ ] Test case 5
- [ ] Test case 6

8) Repeat the tests above with a Status Order Report in the lead case of a consolidated group, and select "Just this case"

Same steps as above.

Expected Results:

[ ] The docket clerk should not have any modal for serving across the group
[ ] The document is served as per normal
[ ] No other cases in the group have the document served on them.

9) Repeat the tests above but create the Status Order Reports with ADC and Chambers staff.

[ ] Tests pass with an ADC
[ ] Tests pass with Chamber Staff

flexion / ef-cms