-
Notifications
You must be signed in to change notification settings - Fork 10
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
Consolidation: Change to QC/Edit Docket Entry Process #10103
Comments
Pre-refinement notes:
|
Note: This story resolves the QC issues described in Scenario 1 above, but does not solve the multiple coversheets that occur when serving simultaneous documents. Another story will address the serving component. |
Test CasesPreconditions
1) Docket clerk accesses the Section QC inbox; Filings made across a consolidated group now display as a singular QC item with all the cases the document was filed in also displayed.
Expected Results:
2) Docket clerk assigns the Consolidated Case QC item to another Clerk; QC item is assigned appropriately.
Expected Results:
3) Docket clerk clicks on the document title from the My Document QC inbox; QC item opens to the QC page on the Lead Case in the Consolidated group.Part 1
Expected Results:
Part 2
Expected Results:
4) Docket clerk completes the QC (does not update the filing info and does not send a message); Document QC is completed for all documents that were filed in the group.
Expected Results:
5) Repeat tests 1-4, but instead Click Complete and Send Message.
6) Docket Clerk Edits the document info during QC for a document that was filed across a consolidated group; Notice of Docket change is generated and docketed in each case in the Consolidated group.
Expected Results:
*Repeat this test but edit the other fields on the QC screen generate a NODC
*Repeat this test but click Complete and Send Message button. 7) Docket clerk accesses a member case where a Petitioner has filed a document across the group, No "Complete QC" link is available from the document preview.
Expected Results:
*Repeat the steps above by checking all of the member cases in the group to ensure that there is no "Complete QC link." 8) Petitioner files a document in a consolidated group that is assigned to a Judge; Judge views their Document QC tab; Filings made across a consolidated group now display as a singular QC item with all the cases the document was filed in also displayed.Preconditions
Expected Results:
*Repeat the test above, but with a Chambers user 9) Docket clerk edits a document in a lead case that was multi-docketed; New alert is displayed on the Edit Docket Entry screen.
Expected Results:
*Note: If you are editing a multi-docketed Simultaneous doc, you will have to Serve the document first. (this will still generate multiple coversheets (see other story that addresses this behavior). After they are all served, THEN you can edit the document 10) Docket clerk makes an edit to the Document information on a document in the lead case; Edits made are reflected on all cases in the consolidated group.
Expected Results:
*Repeat the test above, but edit the other fields on the Document Info tab and review the data on the docket record
DEV Question
11) Docket Clerk makes an edit on the Service tab on a document in the lead case; Edits made are ONLY in the lead case and are NOT reflected on the member cases in the consolidated group.
Expected Results:
12) Docket Clerk clicks the edit link for a document that was multi-docketed on a member case in a consolidated group; New alert is displayed and the data fields on the Document Info tab are disabled.
Expected Results:
13) Docket Clerk makes an edit on the Service tab on a document in a member case; Edits made are ONLY in the member case and are NOT reflected on any of the other member cases or the lead case in the consolidated group.
Expected Results:
14) Docket Clerk makes an edit on the Action(s) tab on a document in the lead case; Edits made are ONLY in the lead case and are NOT reflected on the member cases in the consolidated group.
Expected Results:
15) Docket Clerk makes an edit on the Action(s) tab on a document in a member case; Edits made are ONLY in the member case and are NOT reflected on any of the other member cases or the lead case in the consolidated group.
Expected Results:
16) Docket clerk processes an Order in the lead case in the Consolidated group and serves it across the group; Filings made across a consolidated group now display as a singular QC item with all the cases the document was filed in displayed on the Processed tab of the QC display.
Expected Results:
17) Docket clerk processes an Order in the lead case in the Consolidated group and saves (does not serve); A singular row is displayed on the In Progress tab, and only displays the Lead case docket number; Order is not displayed on any member case in the group as per normal.
Expected Results:
18) Docket clerk processes a paper filing in the lead case in the Consolidated group and serves it across the group; Filings made across a consolidated group now display as a singular QC item with all the cases the document was filed in displayed on the Processed tab of the QC display.
Expected Results:
19) Docket clerk processes a paper filing in the lead case in the Consolidated group and saves (does not serve); A singular row is displayed on the In Progress tab, and only displays the Lead case docket number; paper filing is not displayed on any member case in the group as per normal.
Expected Results:
20) Test with other users
21) Regression stuff
|
As a petitioner or practitioner, so that documents are less confusing, I need the QC process to not generate unnecessary cover sheets on e-filed documents in consolidated cases.
With the implementation of multidocketed e-filings, the QC process now generates multiple unneeded cover sheets for these documents, which make them needlessly long and duplicative. This makes the cover sheets confusing and increases document length for no good purpose.
We would like to handle this process more intelligently for consolidated e-filings. This will streamline the QC/editing process for the Court, reduce overall QC volume, and maintain Court's commitment to having a single source of document truth while removing the extraneous cover sheet generation.
Buckle up.
Pre-Conditions
#10491
Acceptance Criteria
QC PROCESS:
EDIT DOCKET ENTRY PROCESS - LEAD CASE
EDIT DOCKET ENTRY PROCESS - MEMBER CASE:
Notes
Scenario 1 - Simultaneous Briefs that have been filed across a consolidated group
Scenario 2 - Docket clerk needs to edit a filing during QC that has been filed across a consolidated group
Scenario 3 - Docket clerk needs to make an edit that would create a new coversheet to a document that was filed (court filed or externally filed) across a consolidated group
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:
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
UX
Engineering
test
environment if prod-like data is required. Otherwise deployed to anyexperimental
environment.staging
environment.The text was updated successfully, but these errors were encountered: