Issue Summary

If we add "/c/" to the Board settings URL of a TMP Board, it shows Board & Swimlane Settings of a CMP Board instead of showing "Not Found or HTTP 404" error

Irrespective of whether we are on New Navigation UI(Nav4) or Old Navigation UI, if we directly browse to the following URL: https://abc.atlassian.net/jira/software/c/projects/PCA/boards/24/settings/swimlanes or https://abc.atlassian.net/jira/software/c/projects/PCA/boards/24/settings/filter

it starts to show the Board Settings and configuration option of a non-simplified board or CMP Board, although the Board ID belongs to a Simplified Board(TMP Board).

The board settings page should not load as board ID belongs to a TMP Board, and thus the board is a simplified board, so it should show "Not Found" or "HTTP 404" error.

Steps to Reproduce

1. In your site, go to Global Settings>>Personal Jira settings>>Disable "New Navigation"
   
2. Go to Project settings>>Access, of a Team Managed Project & add yourself as an Administrator or Member. 
3. Ensure that you are able to browse the Simplified Board of the Team Managed Project.
4. Now browse directly to the following Company Managed Board Settings(Non-simplified board) URL by adding "/c/" to the URL of the TMP Board(Simplified): https://abc.atlassian.net/jira/software/c/projects/PCA/boards/24/settings/swimlanes 

Expected Results

• It should get redirected to the "Not found" page and show an HTTP 404 Not Found error like below: 
• 
• We should NOT see the Board Settings of a Non-Simplified board for a Simplified board, and also it should show the Location Project as a "Team Managed project". 

Actual Results

We are able to, incorrectly, load the Board Settings page as seen below:

. Also, the TMP Project shows as "Company Managed Project".  This misguides users, and they use the Simplified board as a non-simplified board, ending up creating swimlanes, which will then be not visible on the board and create confusion among users. 

Workaround

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