Describe the Bug
A clear and concise description of what the bug is.
It appears that the yellow sticky icon that displays whenever there is a case note or Judge's note on a case is getting stuck in state and it is displaying for a user when it shouldn't be. For example, I was logged in as a Judge, and I added a Judge note to a case (there were not any case notes on the case, just Judge note). I logged out and logged in as an admissions clerk. When I navigated to the case, the sticky note icon was still present (indicating that there was a note), but when I clicked on the notes tab, there were no notes displayed (as it should be - the judge notes do not display for other users). Once I refreshed the page, the sticky note icon disappeared. I think it is getting stuck in state and being displayed when it shouldn't be?
This is very low priority, as most real users are not logging in/out as different user roles. Most won't ever see this happen in the real world.
Business Impact/Reason for Severity
Low
In which environment did you see this bug?
Staging, Test
Who were you logged in as?
Judge, Admissions Clerk, Trial Clerk, Chambers
What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.)
I noticed this while testing the Postgres Judge's notes story.
To Reproduce
Steps to reproduce the behavior:
Log in as a Judge
Click on one of your upcoming trial sessions
Add in a Note to a case (this is a Judge note and will also be stored on the case)
After adding the Judge note, click on the case docket number (be sure that you remember this docket number for the steps below!)
Notice that the Notes tab has a yellow sticky icon indicating that there is a note on the case
Log out of DAWSON
Log back in as any user that is not in the Judge's Chambers
Navigate to that same case
Notice that there is a yellow sticky note icon on the Notes Tab
Click on the Notes tab
Notice that there isn't any case note
Refresh the page
Now the yellow sticky icon is no longer present on the Notes tab
Expected Behavior
A clear and concise description of what you expected to happen.
Yellow Sticky should not be displayed for users that cannot view judge notes
Actual Behavior
A clear and concise description of what actually happened.
It seems that the yellow sticky note is stuck in state, and that functionality is not refreshing when different users log in/out
Screenshots
If applicable, add screenshots to help explain your problem.
This shows that the case note icon is displaying on the Notes tab when there are no notes visible to the logged in user:
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
[ ] Automated test scripts have been written
[ ] 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. It appears that the yellow sticky icon that displays whenever there is a case note or Judge's note on a case is getting stuck in state and it is displaying for a user when it shouldn't be. For example, I was logged in as a Judge, and I added a Judge note to a case (there were not any case notes on the case, just Judge note). I logged out and logged in as an admissions clerk. When I navigated to the case, the sticky note icon was still present (indicating that there was a note), but when I clicked on the notes tab, there were no notes displayed (as it should be - the judge notes do not display for other users). Once I refreshed the page, the sticky note icon disappeared. I think it is getting stuck in state and being displayed when it shouldn't be?
This is very low priority, as most real users are not logging in/out as different user roles. Most won't ever see this happen in the real world.
Business Impact/Reason for Severity Low
In which environment did you see this bug? Staging, Test
Who were you logged in as? Judge, Admissions Clerk, Trial Clerk, Chambers
What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.) I noticed this while testing the Postgres Judge's notes story.
To Reproduce Steps to reproduce the behavior:
Expected Behavior A clear and concise description of what you expected to happen. Yellow Sticky should not be displayed for users that cannot view judge notes
Actual Behavior A clear and concise description of what actually happened. It seems that the yellow sticky note is stuck in state, and that functionality is not refreshing when different users log in/out
Screenshots If applicable, add screenshots to help explain your problem. This shows that the case note icon is displaying on the Notes tab when there are no notes visible to the logged in user:
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.