Describe the Bug
A clear and concise description of what the bug is.
We received a report from a Court user that the 30 Day Notice of Trial was displaying the wrong city, state on the 30 Day Notice of Trial document. After some investigation, we have determined that the City/State that is displayed on the 30 Day Notice of Trial appears to be pulling from the City/State of Trial Location, rather than the Courthouse address fields.
This became apparent when a trial session that was scheduled for Kansas City, MO had to be changed to Kansas City, KS. The 30 day notice didn't display the correct state, which caused quite a bit of confusion.
Business Impact/Reason for Severity
Med
In which environment did you see this bug?
Prod, Staging
Who were you logged in as?
Case Services Supervisor
What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.)
This issue was reported to us by Court users
To Reproduce
Steps to reproduce the behavior:
Log in as a case services supervisor
Create a new trial Session that is around 25-30 days from the trial session
Be sure that you take note of the Trial Location that you select, as well as the Courthouse Address information
Click Save
QC a couple of pro se cases that do not have counsel
Set the Calendar
Go to a case and take note of the Notice of Trial. It should display the Courthouse address info correctly
Next, go back to the trial session you just created and click Edit
Change the Courthouse address (not the Trial Location), making sure that the City, State of the courthouse address is DIFFERENT than the trial location City, State.
Click Save
Take note of the trial session info on the screen. It should display the updated trial info correctly
Next, click on the Serve/Dismiss link for the 30 day notice
Click yes, Serve
Navigate to the Case and click on the 30 day notice to view the document
Notice that the address of the Courthouse does not display the edited City, State, but instead displays the Trial Location City, State.
I did check, and the original notice of trial displays the correct courthouse address info. This issue appears to only be happening with the 30 day notice.
Expected Behavior
A clear and concise description of what you expected to happen.
Courthouse address info on the 30 day notice should be pointing to the Courthouse address City/State fields.
Actual Behavior
A clear and concise description of what actually happened.
It appears that the 30 Day notice Courthouse address location is point to the Trial Location City/State dropdown field, and this can sometimes cause a mismatch if it is in a different city or state than the requested trial location.
Screenshots
If applicable, add screenshots to help explain your problem.
Here is a screen capture to show that the Courthouse address info is "Jacksonville, MS"
On the 30-Day NOTT, the address info says "Mobile, AL" along with the zip code that I input for Jacksonville.
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Cause of Bug, If Known
Process for Logging a Bug:
Complete the above information
Add a severity tag (Critical, High Severity, Medium Severity or Low Severity). See below for priority definition.
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:
Be focused on solving a user problem
Contain data for all fields in the bug template, so the team can pick it up and begin working immediately
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
[ ] Bug fix has been validated in the Court's test environment
Engineering
[x] Automated test scripts have been written
[x] Field level and page level validation errors (front-end and server-side) integrated and functioning
[ ] Verify that language for docket record for internal users and external users is identical
Describe the Bug A clear and concise description of what the bug is. We received a report from a Court user that the 30 Day Notice of Trial was displaying the wrong city, state on the 30 Day Notice of Trial document. After some investigation, we have determined that the City/State that is displayed on the 30 Day Notice of Trial appears to be pulling from the City/State of Trial Location, rather than the Courthouse address fields.
This became apparent when a trial session that was scheduled for Kansas City, MO had to be changed to Kansas City, KS. The 30 day notice didn't display the correct state, which caused quite a bit of confusion.
Business Impact/Reason for Severity Med
In which environment did you see this bug? Prod, Staging
Who were you logged in as? Case Services Supervisor
What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.) This issue was reported to us by Court users
To Reproduce Steps to reproduce the behavior:
Expected Behavior A clear and concise description of what you expected to happen. Courthouse address info on the 30 day notice should be pointing to the Courthouse address City/State fields.
Actual Behavior A clear and concise description of what actually happened. It appears that the 30 Day notice Courthouse address location is point to the Trial Location City/State dropdown field, and this can sometimes cause a mismatch if it is in a different city or state than the requested trial location.
Screenshots If applicable, add screenshots to help explain your problem. Here is a screen capture to show that the Courthouse address info is "Jacksonville, MS"
On the 30-Day NOTT, the address info says "Mobile, AL" along with the zip code that I input for Jacksonville.
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.