Trying to access nonexistent project board URI may redirect the user to a misleading board UI

Issue Summary

When attempting to access a project board using a URL with a modified (non-existent) board ID, Jira Software Data Center incorrectly tries to load the board that was last successfully accessed, instead of redirecting the user to a more appropriate page or showing a relevant error message.

This behavior may lead to a misleading user interface and error messages, which can cause confusion to users.

Steps to Reproduce

1. Install a vanilla instance of Jira Software Data Center.
   • This was validated on versions 9.4.18, 9.12.5 and 9.14.0.
2. Create a Scrum project with sample data.
   • We will call this project SCRUM.
3. On the SCRUM project, create a new project Scrum board.
   • Let's call this board SCRUM 1.
   • Below is the URL of this board – note the board ID rapidView=4.

     <Jira-Base-URL>/secure/RapidBoard.jspa?rapidView=4
     

4. Configure the SCRUM 1 board with a card color strategy.
   
5. Create a Kanban project with sample data.
   • We will call this project KANBAN.
6. On the KANBAN project, create a new project Kanban board.
   • Let's call this board KANBAN 1.
   • Below is the URL of this board – note the board ID rapidView=5.

     <Jira-Base-URL>/secure/RapidBoard.jspa?rapidView=5
     

7. Access the SCRUM 1 board using the correct board URL.

   <Jira-Base-URL>/secure/RapidBoard.jspa?rapidView=4
   

   • This step is important to trigger the bug.
8. Try to access the KANBAN 1 board, but add any non-digit character to the board id, such as 5^ or 5BLAH.

   <Jira-Base-URL>/secure/RapidBoard.jspa?rapidView=5BLAH
   

Expected Results

Jira redirects the user to the View All Boards page and shows a message similar to the below.

The requested board cannot be viewed because it either does not exist or you do not have permission to view it.

Or Jira shows a You can't view this board message similar to the below.

Actual Results

Jira tries to load the KANBAN 1 board, but loads the issues from the previously seen board, which in the example was SCRUM 1.

As SCRUM 1 had a card color strategy, Jira UI triggers the colors.json request targeting the KANBAN 1 board.
The request fails with a 500 HTTP error, which triggers the following popup error on the UI.

Strategy not supported by the issue index

The JSW logs may show an entry similar to the below:

2024-02-23 10:11:37,761 https-jsse-nio-8443-exec-70 WARN - 611x5061748x3 1gi590s 127.0.0.1 /rest/greenhopper/1.0/xboard/work/5/colors.json [web.rapid.work.WorkResource] GreenHopper REST method failed with SC = 500 - JiraCopiedServerErrorWebException
2024-02-23 10:11:37,762 https-jsse-nio-8443-exec-70 WARN - 611x5061748x3 1gi590s 127.0.0.1 /rest/greenhopper/1.0/xboard/work/5/colors.json [web.rapid.work.WorkResource] JiraCopiedRestErrorCollection[errorMessages=[Strategy not supported by the issue index],errors={}]

All of these errors are misleading, which only happened because Jira tried to load a board with an ID that didn't exist.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.