Closed ttlenard closed 2 years ago
In TEST, when viewing the Pending report for the Chief Judge, the UI indicates that the oldest item is from 7/23/15, however the printable version of the report introduces two entries not seen on the UI, from 2009 and 2014.
Describe the Bug A clear and concise description of what the bug is. When you run the pending report, it is sorted by date in the UI, but if you click on printable report, the PDF that is generated is no longer sorted by filed date, and the entries on the report appear to be in a random order.
Please refer to 2156 for the Original story that indicates results need to be sorted by date.
This was reported by Susan Culbreath in ADC.
Business Impact/Reason for Severity
In which environment did you see this bug? Production
Who were you logged in as? ADC
What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.) Using the application
To Reproduce Steps to reproduce the behavior:
Expected Behavior A clear and concise description of what you expected to happen.
Results on the printable report are the same as what appears in the UI (Showing results that are sorted by filed data (oldest to newest)
Actual Behavior A clear and concise description of what actually happened.
Results on the printable report are displayed in a random order, rather than sorted by date filed.
Screenshots If applicable, add screenshots to help explain your problem.
Here is the pending report in the UI - notice the order of the file dates:
Here is the printable report - notice the order of the file dates - they do not match what is in the UI.
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