Issue Summary

When searching issues using the detailed view in the issue navigator, it's possible that using the back button on the browser causes Jira to display a different issue than expected in the URL of the address bar.
 

Steps to Reproduce

1. Create a saved filter that will return epics, tasks, and subtasks in the search results.
2. load that saved filter, and make sure you're in the detailed view (not list view), the URL should look like this https://examplesite.atlassian.net/browse/ABC-123?filter=10023 specifically using the /browse/ endpoint here.
3. Select a child issue, like a subtask, from the left panel's search results. In this case choose ABC-123 the URL should remain https://examplesite.atlassian.net/browse/ABC-123?filter=10023
4. Then click the breadcrumb link to the parent issue (note the URL will change to something like https://examplesite.atlassian.net/browse/ABC-100?filter=10023 )
5. Then press the back button on your browser

Expected Results

We expect to have the navigator return to the previous issue

Actual Results

While the URL will change in the address bar to the previous issue, the page does not change back to that issue. And instead continues to show the previous issue, but with an incorrect selection of breadcrumb links. This relates to another documented JRACLOUD-81276

Workaround

1. for customers who have the new issue navigator experience available for their sites they can switch to the new experience to prevent this bug.
2. If the saved filter is only selecting from a single project (say the project key is SSP for example), then it is possible to work around this by using the Project Issue Navigator instead. This can still then display the issues in that saved filter for that project, but without this bug behavior. The URL will be different when viewing this, such as https://examplesite.atlassian.net/jira/software/c/projects/SSP/issues/SSP-25?filter=10010. Whereas if using the issue navigator directly in https://examplesite.atlassian.net/issues/?filter=10010 you can still see this bug behavior. If the saved filter contains more than project, or no specific projects, then this workaround is not viable