Issue Summary

When an issue is deleted in a separate browser tab, the original tab retains the issue in its JQL search results list (expected point-in-time snapshot). However, when the user clicks the deleted item from this list, the Issue Detail modal/sidebar loads in an ambiguous, broken state: it populates the header/fields using client-cached metadata while individual asynchronous components fail with generic errors (e.g., "We couldn't load the history feed"), rather than rendering a standard "Issue Not Found / Deleted" error screen.

Steps to Reproduce

1. In Browser Tab 1, run a JQL search that includes a target test issue (e.g., TEST-38).

1. Open TEST-38 in a new browser tab (Tab 2).

1. In Tab 2, delete TEST-38.

1. Switch back to Tab 1 (do not refresh or re-run the search).

1. In Tab 1's search results list, click on TEST-38 to open the issue modal/side bar.

Expected Results

The modal-sidebar / detail view catches the 404 response on the primary issue fetch and renders a clean, user-friendly error state (e.g., "This issue doesn't exist or has been deleted").

Actual Results

• The modal/sidebar opens and displays partial cached metadata from the list row.

• Asynchronous deep fetches fail silently or display fragmented inline errors (e.g., "We couldn't load the history feed").

• The user is left with a broken UI state until they manually close the modal and refresh the search.

Workaround

Refresh the browser tab or re-execute the JQL search.