Open cholly75 opened 1 year ago
Pre-refinement questions:
In the add/edit docket entry field for all orders a new checkbox should be added above the inclusion/attachments checkbox.
If there are no motions on the docket record, the dropdown should say "There are no motions on the docket record".
If the user clicks a motion is being disposed but does not select a motion and/or its status, display validation messages.
*Pre-Conditions - Be sure that the case you are on has a few motions on the docket record.
Expected Results:
Expected Results:
Expected Results:
Part 1
Expected Results:
Part 2
Expected Results:
Part 3
Expected Results:
Expected Results:
*Pre-Conditions - Be sure that the case you are on has a few motions and Orders on the docket record.
Expected Results:
Expected Results:
Part 1
Expected Results:
Part 2
Expected Results:
Part 3
Expected Results:
Expected Results:
Expected Results:
Expected Results:
*Repeat this test with other external users (Petitioner, IRS, Practitioner, Terminal user)
As a party to a case, so that I can quickly tell the disposition of a particular motion, I need motions to indicate their disposition and connection to the dispositive Order.
Currently when an order granting or denying a motion is docketed, there is no indication on the motion docket entry or in the motion data of how it has been disposed. This means that to find out whether a particular motion has been granted or denied the docket record and orders must be scanned and parsed individually for the order doing so. This makes it difficult to see at a glance the disposition of the motion for parties to the case and Court personnel.
Additionally, this makes it difficult to report out on operational Court data regarding types and behaviors w/r/t motions. For example, the Court is interested in monitoring how many Motions for Summary Judgment are granted vs. denied, but because there's no explicit connection between the motion itself and the order disposing of it, these statistics are difficult to collect with any degree of accuracy.
This story will address an order disposing of a single motion.
We would like to keep this behind a feature flag pending the full rollout of use cases.
Pre-Conditions
Acceptance Criteria
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:
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
.