GitLab issues navigation tab should only be associated with GitLab issues
Background
- Currently, if you configure JIRA integration on per a project, GitLab issues is essentially disabled.
- When you click on the Issues link in the navigation, GitLab redirects you to JIRA. This should not be the case.
- Clicking on the Issues link should bring you to GitLab issues as normal.
- You should be able to use GitLab issues normally even when you have JIRA integration on. All features of GitLab issues work, including all integrations with merge requests.
Description
- The GitLab issues tab/link in the main navigation for a project should be visible, if the GitLab issues functionality is configured on in the project settings.
- When you click on the issues tab/link, it goes to the GitLab issues list.
- If the GitLab issues functionality is configured off in the project settings, then the issues tab should not be visible.
- When you configure any external integrated issue tracker within GitLab (e.g. JIRA, Redmine), that does not affect the GitLab issues tab/link in any way. The GitLab issues link never goes to an external location. It only goes to the GitLab issues list.
Blocked by
- This should not be merged until https://gitlab.com/gitlab-org/gitlab-ce/issues/33679 is merged first.
Related
Edited by Victor Wu