Disable GitLab issues when enabling external issue trackers
Problem
When setting up external issue trackers like Jira, GitLab issues stay enabled. Currently, there is messaging on the configuration screen that recommends that customers disable GitLab issues when using external issue trackers.
However, as we work towards adding the ability to create Jira issues from other places in the application, like:
- Creating an issue from a found vulnerability: #8942 (closed)
- Creating an issue from a failed pipeline job: #18731
- Creating an issue from unresolved threads in an MR: #249579
We run into the problem of having to now offer more than one issue tracker to create the issue in.
Example of creating a new issue from a failed pipeline job:
No integrations enabled | Jira issues enabled (not recommended) | Jira issues enabled, GitLab issues disabled (Ideal state) |
---|---|---|
Example of creating a new issue from an unresolved MR:
No integrations enabled | Jira issues enabled (not recommended) | Jira issues enabled, GitLab issues disabled (Ideal state) |
---|---|---|
Proposal
Ideally, there are better defaults in places which discourages this type of productivity anti-patterns.
When setting up the Jira issue list integration (or any other external issue tracker), we should:
- Pro-activity disable GitLab issues (still allow it, but not encourage it) #328606[disable-gl-issues-prompt.png]
- Communicate whether or not other external issues trackers are already enabled #328470 (closed)
Please leave comments in the Designs section below.