You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a judge or chambers user, so that I can quickly order a motion response, I need to be able to generate an order that directs a party to respond to a motion.
Sometimes when motions are filed they need a response from the opposing party. In these cases, the Court directs the opposing party to respond to the motion with a filing. Since these orders are typically boilerplate orders, we would like to follow the examples set by stamp grant/deny and status report orders and provide a UI with selectable options that will generate said order using approved text.
See stories for Status Report Order (#10102) and Stamp Disposition (#9479) for examples of how we have approached this in the past.
Pre-Conditions
Acceptance Criteria
Order Response workflow can be invoked from the Document View of a motion or a Message with the motion attached.
Order response workflow contains the following fields for input:
Response Date (Required - Date field)
Order Reply? (Optional - Check box)
Order Reply/SR? (Optional - Check box)
Only one of the two boxes here may be checked
Reply Date (Activated+Required when either "Order Reply?" or "Order Reply/SR?" box is checked - Date field)
Additional text - 240 character limit (Optional - long text box)
User can select option(s) then generate a preview of the PDF order
If the case is the lead case in a consolidated group, user must choose whether or not to generate the order in all cases in the CG
If user selects to generate in all cases in the CG, caption is updated appropriately (et al., docket numbers)
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
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.
The text was updated successfully, but these errors were encountered:
katiecissell
added
UX in Progress
General UX work being done [excluding research or design efforts], development should not begin.
and removed
UX Needed
General UX work is needed (this work does not fall into the 'design' or 'research' bucket)
labels
Feb 7, 2025
Add "Order Response" to document view. Validation will display if required fields are not filled in or filled in incorrectly. UI is very similar to the status report order flow.
As a judge or chambers user, so that I can quickly order a motion response, I need to be able to generate an order that directs a party to respond to a motion.
Sometimes when motions are filed they need a response from the opposing party. In these cases, the Court directs the opposing party to respond to the motion with a filing. Since these orders are typically boilerplate orders, we would like to follow the examples set by stamp grant/deny and status report orders and provide a UI with selectable options that will generate said order using approved text.
See stories for Status Report Order (#10102) and Stamp Disposition (#9479) for examples of how we have approached this in the past.
Pre-Conditions
Acceptance Criteria
Notes
MR_Template.pdf
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
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
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: