Extend Multiple Iteration Filing/Editing to Docket Clerks

cholly75 commented 1 year ago

As a docket clerk, so that I can appropriately indicate the correct iteration of a particular filing, I need to be able to enter the 16th or later iteration of a filed document.

In #8780 we introduced the ability to file multiple iterations of a document beyond the 3rd for e-filers.

The work done here appears to be present for docket clerks in QCing these e-filings and when entering uploading paper filings; however, if the "Other" selection on the dropdown menu is selected and a number filled in the Iteration field, upon completing QC or saving/serving the filing an incorrect validation is triggering, telling the user they need to enter a number in the Iteration field.

Pre-Conditions

Acceptance Criteria

Docket clerk can complete QC on a filing when editing the 16th or later iteration of the filing
Docket clerk can save/serve a paper filing of the 16th iteration or later
Functionality remains otherwise identical to the e-filing use case

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

[x] Automated test scripts have been written, including visual tests for newly added PDFs
[x] Field level and page level validation errors (front-end and server-side) integrated and functioning
[x] Verify that language for docket record for internal users and external users is identical
[x] New screens have been added to pa11y scripts
[x] All new functionality verified to work with keyboard and macOS voiceover https://www.apple.com/voiceover/info/guide/_1124.html
[x] READMEs, other appropriate docs, JSDocs and swagger/APIs fully updated
[x] UI should be touch optimized and responsive for external only (functions on supported mobile devices and optimized for screen sizes as required)
[x] Interactors should validate entities before calling persistence methods
[x] Code refactored for clarity and to remove any known technical debt
[x] Acceptance criteria for the story has been met
[x] If there are special instructions in order to deploy into the next environment, add them as a comment in the story
[x] 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.

rosiehsmith commented 1 year ago

Since this is an 8780 bonus feature (read: missed flows with a reused form, e.g. paper filling, document QC) I don’t think it’s necessary to refine or do UX research / design, which is why I moved it straight to “Needs Test Cases.” I have a fix for this, but I do want to ensure these flows are thoroughly tested.

ttlenard commented 1 year ago

Test Cases

1) Docket clerk QC's an e-filed document that has 16-999 iterations; document saves/completes appropriately.

Preconditions:

Be sure that you have logged in as a Petitioner and Practitioner and filed documents that require the user to select an Iteration. (Amended, Amendment, Supplement, Supplemental, Stipulation of Facts)
When you are filing and you select the iteration value, select Other, and then type in a value between 16-999
Log in as a docket clerk
Click on Document QC
Click on Section Document QC
Find one of the e-filed documents that you just submitted and click on the document link.
Make sure that the document has Other in the "What iteration is this filing?" field
Make sure that there is a value from 16-999 in the Iteration field.
Click Complete

Expected Results:

[x] NEW FUNCTIONALITY - No validation errors appear
[x] User is taken back to the Document QC tab and there is a Green Confirmation message indicating that the document has been completed.
[x] After clicking on the Processed tab, the document you just QC'd is present.
[x] After clicking on the Docket number of the document you just QC'd, you can view it as normal on the docket record.

*Be sure that you repeat this with all of the document types that can have iterations.

2) Docket Clerk edits the iteration value while QCing an e-filed document that has 16-999 iterations; document saves/completes appropriately.

Preconditions:

Be sure that you have logged in as a Petitioner and Practitioner and filed documents that require the user to select an Iteration. (Amended, Amendment, Supplement, Supplemental, Stipulation of Facts)
When you are filing and you select the iteration value, select Other, and then type in a value between 16-999
Log in as a docket clerk
Click on Document QC
Click on Section Document QC
Find one of the e-filed documents that you just submitted and click on the document link.
Make sure that the document has Other in the "What iteration is this filing?" field
Make sure that there is a value from 16-999 in the Iteration field.
Change the iteration value to something else (a value in the iteration "Other", as well as changing it to a value from 1-15)
Click Complete

Expected Results:

[x] NEW FUNCTIONALITY - No validation errors appear
[x] User is taken back to the Document QC tab and there is a Green Confirmation message indicating that the document has been completed.
[x] After clicking on the Processed tab, the document you just QC'd is present.
[x] After clicking on the Docket number of the document you just QC'd, you can view it as normal on the docket record.

*Be sure that you repeat this with all of the document types that can have iterations.

3) Docket Clerk edits the iteration value after QCing an e-filed document; Document saves/completes appropriately.

Log in as a docket clerk
Click on Document QC
Click on Section Document QC
Click on the document link for any document (doesn't have to be a document with an iteration)
Click Complete
Click on the Processed tab
Click on the docket number of the document you just QC'ed
Click on the Edit button next to the document that you just QC'd
Either change the document type to a document that has an iteration, or if it was already one of those documents, change the iteration value to a different number (be sure to test with the normal dropdown value as well as a value from 16-999)
Click Save

Expected Results:

[x] NEW FUNCTIONALITY - No validation errors appear
[x] Green confirmation banner above the docket record, message indicates that Docket Entry changes were saved.

*Be sure that you repeat this with all of the document types that can have iterations.

4) Docket clerk QC's a paper filed document that has 16-999 iterations; document saves and is sent for service appropriately.

Log in as a docket clerk
Navigate to a case
Click on Create
Select Paper Filing
Upload or Scan in a document
While filing out the data about the document, be sure that you select a document that requires an iteration value
Select Other, and then input a value that is 16-999
Be sure all required fields are filled in.
Click Save and Serve

Expected Results:

[x] NEW FUNCTIONALITY - No validation errors appear
[x] The "Are you ready to Initiate Service" pop-up modal appears
[x] After clicking "Yes, Serve", Print for paper service page appears
[x] After clicking "Done" on the print for paper service screen, there is a green confirmation message above the docket record indicating that the entry has been added to the docket record.

*Be sure that you repeat this with all of the document types that can have iterations.

flexion / ef-cms