BUG: Filtering by documents on the docket record and data entered into the advanced search are persisting

[ttlenard]

Describe the Bug
A clear and concise description of what the bug is.
We've noticed that some data is sticking around, when it should probably be getting cleared. Some examples of this are:

1. Filter Persistence
When a user filters the docket record by certain documents, that filter doesn't clear out when the user navigates to a different case. The filter is persisting. We've even noticed while testing that if the user logs out and comes back in, that filter is still in place. We've even tested by logging out and then logging in as a different user. The docket record filter should probably be clearing out when navigating away from the case.

2. Search Persistence
When a logged in user is searching on the Advanced search page. Users can search by case, order, opinion, and practitioner and when they go back to any of these search tabs, their previous search and results is still present. We've even noticed while testing that if the user logs out and comes back in, that search results are still in present. We've even tested by logging out and then logging in as a different user. The search results should probably be clearing out when navigating away from any of the search tabs.

Business Impact/Reason for Severity
low

In which environment did you see this bug?
Prod, test

Who were you logged in as?
Any logged in user

What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.)
Testing other functionality

To Reproduce
Steps to reproduce the behavior:
Filter persistence

1. Log in as any Court user
2. Navigate to a case that has a lot of documents to filter
3. Filter by a document type
4. Navigate to another case
5. Notice that the Filter is still present (This is issue 1 - shouldn't be happening)
6. Log out and log back in as a different user (also can be the same user, doesn't matter)
7. Navigate to a case, notice that the filter is still in place. (This is issue 2 - shouldn't be happening)

Search Persistence

1. Log in as any user
2. Search for case, order, opinion, and practitioner
3. Navigate to somewhere else in the application
4. Next, navigate back to the Advanced Search page
5. Notice that the searches are still present (This is issue 1 - shouldn't be happening)
6. Next, log out
7. Log in as a different user (also can be the same user, doesn't matter)
8. Navigate to the advanced search page
9. Notice that your searches are still present. (This is issue 2 - shouldn't be happening)

Expected Behavior
A clear and concise description of what you expected to happen.
Filters - When a user navigates away from the case, the filters should clear
Searches - when a user clicks on a different search tab or if they navigate away from the search page, the previous search term that they searched for should not be staying persistent

For both - After a user logs out, the filters/search should not display again when they come back in (or even a different user)

Actual Behavior
A clear and concise description of what actually happened.
Filtering by documents on the docket record and data entered into the advanced search are persisting on the page after users navigate away from the case/tab, and even after logging out and logging back in to DAWSON (Even as different users).

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.