As a Court user, so that my Orders I generate in lead cases in a consolidated group are formatted correctly, I need the current text "Docket No." to be formatted to "Docket Nos." to reflect multiple docket numbers on the Order.
We received feedback from the Court that the orders generated in Consolidated cases have a minor formatting issue when the user clicks on the "Add Docket Numbers to the Caption Link" to add more docket numbers to the Order, so we'd like to correct this.
Pre-Conditions
Acceptance Criteria
When a user clicks on the "Add Docket Numbers to the Caption" link to add additional docket numbers to a generated Order, display "Docket Nos." in front of the docket numbers.
Do not display "Docket Nos." if the order being generated is for a singular docket number. In this scenario, keep the display as "Docket No."
Notes
Current display when there are multiple docket numbers added to an order. Private Zenhub Image
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:
[x] Is framed in business/user need, the value has been addressed.
[x] Includes acceptance criteria
[x] Has been refined
[x] 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
[x] Swagger docs have been updated if API endpoints have been added or updated.
[ ] UI should be touch optimized and responsive for external users.
[x] Interactors should validate entities before calling persistence methods.
[x] Features have been optimized where possible to reduce response times. For example, reducing api response times, parallelizing client network calls, optimizing database reads, etc.
[x] Types have been added to all added and updated functions.
[x] Code refactored for clarity and to remove any known technical debt.
[x] 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.
[x] 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:
1) Court user creates an Order in the lead case in a consolidated group; Adds docket numbers; Order header info displays "Docket Nos.".
Log in as a Court User
Navigate to the lead case in a consolidated group
Click on the Create Menu, and then select Order or Notice
Select any of the Orders from the Dropdown menu
Click Continue
Add in some sample text in the Generate Order text area
Click on Add Docket Numbers to the caption link
Be sure that you have more than one docket number selected and select Add Docket Numbers button
Click the Preview tab
Expected Results:
[x] NEW FUNCTIONALITY - Docket Nos. is now displayed, followed by the list of docket numbers that you had selected in the previous steps.
2) Court User applies a signature and saves the draft Order; Order header info displays "Docket Nos.".
Continuing from the previous test
Click save
Apply the Judges Signature and then click Save Signature
Expected Results:
[x] NEW FUNCTIONALITY - In the saved draft, Docket Nos. is now displayed, followed by the list of docket numbers that you had selected in the previous test.
3) Court user creates an Order in the lead case in a consolidated group; does NOT add any additional docket numbers, Order header info displays "Docket No.".
Log in as a Court User
Navigate to the lead case in a consolidated group
Click on the Create Menu, and then select Order or Notice
Select any of the Orders from the Dropdown menu
Click Continue
Add in some sample text in the Generate Order text area
Do not click the link to add additional docket numbers to the caption
Click the Preview tab
Expected Results:
[x] "Docket No." is displayed in the Order header, followed by the singular docket number of the lead case
[x] After saving and applying a signature, the "Docket No." is what is displayed in the saved draft.
4) Court User creates an Order in the Lead case in a consolidated group; adds additional docket numbers, then removes additional docket numbers; Docket No text in the Order Header is updated appropriately.
Log in as a Court User
Navigate to the lead case in a consolidated group
Click on the Create Menu, and then select Order or Notice
Select any of the Orders from the Dropdown menu
Click Continue
Add in some sample text in the Generate Order text area
Click on Add Docket Numbers to the caption link, select multiple cases
Preview the Order (Should have "Docket Nos.")
Click on the Edit Docket numbers on caption link
Only check the lead case docket number
Expected Results:
[x] NEW FUNCTIONALITY - The "Docket No." text is responsive to adding/editing docket numbers and displays appropriately on both the preview and the saved draft document.
As a Court user, so that my Orders I generate in lead cases in a consolidated group are formatted correctly, I need the current text "Docket No." to be formatted to "Docket Nos." to reflect multiple docket numbers on the Order.
We received feedback from the Court that the orders generated in Consolidated cases have a minor formatting issue when the user clicks on the "Add Docket Numbers to the Caption Link" to add more docket numbers to the Order, so we'd like to correct this.
Pre-Conditions
Acceptance Criteria
Notes
Current display when there are multiple docket numbers added to an order.
Private Zenhub Image
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:
Definition of Done (Updated 5-19-22)
Product Owner
UX
Engineering
efcms-local.json
, 3 local s3 files corresponding to that docketEntryId have been added toweb-api/storage/fixtures/s3/noop-documents-local-us-east-1
.