JIRA Integration no longer blocks access to GitLab issues
Summary
On gitlab.com JIRA integration no longer blocks access to the issues page. Previously if JIRA integration was enabled, the issues link would forward to an external Jira site and creation of issues/milestones/labels/boards would be disallowed. Now users can see the issue pages and sub-menu and create issues/milestones/labels/boards in Gitlab. It may have regressed with the flyout menu support in #34026 (closed) since that RC is when it appeared, but just a guess. It seems to occur on both the old nav and the new nav.
Steps to reproduce
- Enable JIRA integration for a project and verify it is working.
- Click the Issues menu on the sidebar for that project.
Example Project
https://gitlab.com/ssheehy/jira-issues-menu
What is the current bug behavior?
On 9.5 RC on gitlab.com with JIRA integration enabled, when clicking the issues menu it takes you to the GitLab issues page where you can create and view issues. It also expands the sub-menu so you can see and visit List, Boards, Labels and Milestones pages. Users can create issues in GitLab even though JIRA is our exclusive source for tickets.
What is the expected correct behavior?
On 9.4, JIRA Integration would cause the issues menu to be a link directly to the external JIRA site. No other sub-menu would be displayed because you would be redirected to an external site. This also effectively disallowed issues, milestones, boards and labels to be created in Gitlab. This is what we want since we are using JIRA to do all these things currently and only using GitLab for code hosting. Issues should be allowed only in JIRA or in GitLab, but not both.
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
NA
Results of GitLab application Check
NA
Possible fixes
NA