BUG: Sorting by Docket number or Case status and then checking the message complete checkbox causes messages to jump to a different location in the sort order.

[ttlenard]

Describe the Bug A clear and concise description of what the bug is.

This bug was reported to us by a Court user. It appears that if a Court user sorts their message inbox by docket number, and they happen to have multiple messages from the same docket number, and they click on the checkbox to complete the message, the sort order changes, and the message that they just selected jumps to a different location in the message inbox table.

This is also occurring if the user sorts by Case Status.

This caused quite a bit of confusion to the Court user when this occurred. It seems that selecting the checkbox is somehow changing the sort order when the user has sorted the messages inbox by docket number or Case status.

Business Impact/Reason for Severity low severity

In which environment did you see this bug? Prod/Test

Who were you logged in as? Judge Buch

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:

1. Log in as Judge Buch
2. Click on Messages
3. Be sure that your message inbox has at least 3 messages from the same case
4. Click on the Docket number header to sort the message table by docket number
5. Click on one of the checkboxes for one of the messages from the case identified in step 3
6. Notice that the message just "jumped" to a new spot in the table
7. Uncheck the checkbox, and notice that the original sort order is back.
8. You can check/uncheck any of the messages from this case and it will continue to "jump" to a different sort order.
9. Repeat the steps above, but instead of docket number, sort by the Case Status column, and attempt to check the box for one of the messages from the case in step 3
10. Notice that your message will "jump" to a different sort order.

Video of the bug: https://github.com/user-attachments/assets/e10ebfc5-1810-46e5-b1bd-65a23ca74bcf

Expected Behavior A clear and concise description of what you expected to happen. Checking the complete box for a message should not result in the message "jumping" to a new location in the sort order in the table.

Actual Behavior A clear and concise description of what actually happened. When sorting by either Docket number or Case Status, checking the complete box on a message where there are other messages from the same case causes the sort order to "jump" around.

Screenshots If applicable, add screenshots to help explain your problem.

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
• [ ] New screens have been added to pa11y scripts
• [ ] All new functionality verified to work with keyboard and macOS voiceover https://www.apple.com/voiceover/info/guide/_1124.html
• [ ] READMEs, other appropriate docs and swagger/APIs fully updated
• [ ] UI should be touch optimized and responsive for external only (functions on supported mobile devices and optimized for screen sizes as required)
• [ ] Interactors should validate entities before calling persistence methods
• [ ] Code refactored for clarity and to remove any known technical debt
• [ ] Deployed to the Court's test environment if prod-like data is required. Otherwise, deployed to any experimental environment for review.