Closed cholly75 closed 2 years ago
@swongCO @liadmccabe This story still needs UX added. When the court adds the documents that require cover sheets, these documents are not served to parties, they are just saved to the docket record. Will need to have design added for a new modal for this workflow, since the existing modal states "are you ready to initiate service?" when selecting cases in a CG. Thanks!
Documents that aren't served only have Save Entry / Cancel as CTAs on the Drafts page:
When the user clicks Save Entry, display the modal with the list of cases: Text changes:
When the user clicks Yes, Save, follow existing flow and take the user to the docket record page with a confirmation message:
Expected Results
Expected Results
Expected Results:
Expected Results
Expected Results
Expected Results
Expected Results
Expected Results:
Expected Results
Expected Results
Expected Results
Expected Results
Expected Results:
Expected Results
Expected Results
Expected Results
Expected Results
Expected Results:
Expected Results
Expected Results
Expected Results:
Expected Results
Expected Results:
Expected Results
Expected Results
Started prep work on story. Will continue pending path taken in #3569.
I talked with @halprin about this story and there are a couple of things we want to clear up with @cholly75 before we continue working on this feature. We are confused why the modal pops up for the save entry
button, but it was discussed that only serving it would show the modal.
Comments from Court post-demo: decision was made to NOT reflect on the cover sheet caption any docket numbers in the consolidated group that the document was NOT filed in. Spoke w/ Cody, sending back to In Progress.
CC: @ttlenard - will need to adjust test cases to account for direction change w/r/t docket numbers captured on the, er, caption.
@cholly75 Test cases above have been updated to reflect the changes suggested. Docket numbers that were NOT selected in the modal should not be reflected on the cover sheet.
As a docket clerk, in order to prevent having to add multiple docket entries in a group of consolidated cases, I need the system to automatically add an unservable docket entry to any other cases in the group that I choose when adding a docket entry for a Draft in the Lead case.
When a document is filed in the Lead Case of a consolidated group, usually it also needs to be filed in the other cases in the group as well. Currently the functionality developed in #3569 only targets documents intended to be served on parties.
We would like to extend this functionality to documents that are coded as unservable as well. Of these documents, a subset also receive cover sheets and so we need to address the creation of these cover sheets as part of this story like so:
We would like cover sheets generated for documents filed in consolidated cases to reflect all the cases in the consolidated group and the document docket positions in those cases. This story addresses court-filed documents, but will be required functionality when we extend consolidated case improvements to party-filed documents.
See screenshots for visuals.
Pre-Conditions
3569
Acceptance Criteria
Notes
Example:
Tasks
Test Cases
Story Definition of Ready (Created on 9/26/21)
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 10-6-21)
Product Owner
UX
Engineering
test
environment for PO Review