cholly75
commented
1 year ago Dockets to check for status change on 9/12:
Answer (A) - 122-22 / 11 Answer to Amended Petition, as Amended (ATAP) - 2600-22 / 11 Answer to Amendment to Amended Petition (AAAP) - 2724-22 / 4 Answer to Amendment to Petition (AATP) - 1832-22 / 12 Answer to Petition, as Amended (APA) - 606-22 / 12 Answer to Second Amended Petition (ATSP) - 3976-22 / 4 Answer to Second Amendment to Petition (AATS) - 4550-22 / 5 Answer to Supplement to Petition (ASUP) - 3131-22 / 11 Answer to Third Amended Petition (ASAP) - 8414-22 / 8 Answer to Third Amendment to Petition (AATT) - 4646-22 / 6
CONFIRMED - all flipped status as expected.
Describe the Bug The logic for changing the case status automatically from General Docket - Not At Issue to General Docket -At Issue (Ready for Trial) as per the original story #1187 is supposed to look at multiple event codes in conjunction with a 45-day elapsed time to determine whether the case should change status.
In production, we see several examples of cases where an Answer-type document has been filed and the necessary time has elapsed but no status change occurred. We need to make sure the logic is taking into account all of the appropriate Answer-type event codes on the docket record when processing each night. Currently it appears that only Answer (A) documents are being processed.
The list of all Answer-type codes as per the original story:
Answer (A) Answer to Amended Petition (AAPN) Answer to Amended Petition, as Amended (ATAP) Answer to Amendment to Amended Petition (AAAP) Answer to Amendment to Petition (AATP) Answer to Petition, as Amended (APA) Answer to Second Amended Petition (ATSP) Answer to Second Amendment to Petition (AATS) Answer to Supplement to Petition (ASUP) Answer to Third Amended Petition (ASAP) Answer to Third Amendment to Petition (AATT)
The presence of any of these on the docket record should be accounted for in the logic that runs each night to change the case status.
Business Impact/Reason for Severity Cases that should otherwise be eligible for calendaring for trial are not appearing on the eligible case list as their status remains "General Docket - Not At Issue". We have several cases that have been awaiting a trial date for over a year now.
In which environment did you see this bug? PROD
Who were you logged in as? Docket clerk
What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.) Investigating report from docket
To Reproduce Examples of cases where the status has not changed as expected (manually updated in PROD, still present in TEST): 16271-22 13817-22
Expected Behavior A clear and concise description of what you expected to happen.
Actual Behavior A clear and concise description of what actually happened. Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Cause of Bug, If Known
Process for Logging a Bug:
Severity Definition:
Critical Defect Blocks entire system's or module’s functionality No workarounds available Testing cannot proceed further without bug being fixed.
High-severity Defect Affects key functionality of an application There's a workaround, but not obvious or easy App behaves in a way that is strongly different from the one stated in the requirements
Medium-severity Defect A minor function does not behave in a way stated in the requirements. Workaround is available and easy
Low-severity Defect Mostly related to an application’s UI Doesn't need a workaround, because it doesn't impact functionality
Definition of Ready for Bugs(Created 10-4-21)
Definition used: A failure or flaw in the system which produces an incorrect or undesired result that deviates from the expected result or behavior. (Note: Expected results are use cases that have been documented in past user stories as acceptance criteria and test cases, and do not include strange behavior unrelated to use cases.)
The following criteria must be met in order for the development team to begin work on the bug.
The bug must:
Process: If the unexpected results are new use cases that have been identified, but not yet built, new acceptance criteria and test cases should be captured in a new user story and prioritized by the product owner.
If the Court is not able to reproduce the bug, add the “Unable to reproduce” tag. This will provide visibility into the type of support that may be needed by the Court. In the event that the Court cannot reproduce the bug, the Court will work with Flexion to communicate what type of troubleshooting help may be needed.
Definition of Done (Updated 4-14-21)
Product Owner
Engineering
testenvironment if prod-like data is required. Otherwise, deployed to anyexperimentalenvironment for review.