Deprecation of Jira GitHub Enterprise DVCS Integration

For guidance on the overall deprecations, removals and breaking changes workflow, please visit https://about.gitlab.com/handbook/product/gitlab-the-product/#breaking-changes-deprecations-and-removing-features

Deprecation Summary

The Jira DVCS Connector will no longer support Jira Cloud users starting with GitLab 16.0. The GitLab for Jira App has always been recommended for Jira Cloud users, and it will be required instead of the DVCS connector. If you are a Jira Cloud user, it is recommended to begin the migration to the Jira App.

Any Jira Server and Jira Data Center users will need to confirm they are not using the GitHub Enterprise Connector to enable the GitLab DVCS integration, but they may continue to use the native GitLab DVCS integration (supported in GitLab 8.14 and later).

Breaking Change

This is a breaking change as it will remove support for the GitHub Enterprise Connector, impacting GitLab.com users leveraging the Jira/GitLab DVCS Connector integration.

Users can either migrate to the GitLab for Jira App (required for Jira Cloud users), or they may use the native GitLab DVCS Connector without the GitHub Enterprise DVCS Connection (for Jira Server or Jira Data Center users).

Affected Topology

Any users of the GitHub Enterprise Connector is affected by this change, which could impact any combination of users: GitLab.com/Self-Managed + Jira Cloud/Jira Server/Jira Data Center. GitLab released our Native GitLab DVCS Integration in %8.14 which allowed users to move off of the GitHub Enterprise Connector. This update will remove the legacy connector.

	Jira for GitLab App	Jira DVCS GitLab Connector	Jira DVCS GitHub Connector	GitLab Jira Integration
Jira Cloud + GitLab.com User	✅	❌	💀	✅
Jira Server/Data Center + GitLab.com User	❌	✅	💀	✅
Jira Cloud + GitLab SM User	⏳	❌	💀	✅
Jira Server/Data Center + GitLab SM User	❌	✅	💀	✅

✅ Supported and recommended
☑ Supported but not recommended
⏳ Planned, and already possible with workarounds
❌ Not supported
💀 Deprecated

Affected Tiers

Free
Premium
Ultimate

Checklists

Labels

This issue is labeled deprecation, and with the relevant ~devops::, ~group::, and ~Category: labels.
This issue is labeled breaking change if the removal of the deprecated item will be a breaking change.

Timeline

Please add links to the relevant merge requests.

As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule: 14.8, 14.9, 14.10, 15.0 – 14.8 is the third milestone preceding the major release):
- A deprecation entry has been created so the deprecation will appear in release posts and on the general deprecation page. https://docs.gitlab.com/ee/update/deprecations#jira-github-enterprise-dvcs-integration
- Documentation has been updated to add a note about the end-of-life and to mark the feature as deprecated.
On or before the major milestone: A removal entry has been created so the removal will appear on the removals by milestones page and be announced in the release post.
On the major milestone:
- The deprecated item has been removed. Docs MR !117581 (merged)
- If the removal of the deprecated item is a breaking change, the merge request is labeled breaking change.

Mentions

Your stage's stable counterparts have been @mentioned on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager.
- To see who the stable counterparts are for a product team visit product categories
  - If there is no stable counterpart listed for Sales/CS please mention @timtams
  - If there is no stable counterpart listed for Support please mention @gitlab-com/support/managers
  - If there is no stable counterpart listed for Marketing please mention @cfoster3
Your GPM has been @mentioned so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change.

Deprecation Milestone

%15.0

Planned Removal Milestone

%16.0

Implementation plan

Remove the v3 API.This is an API that behaves like the GitHub Enterprise API so Jira can connect to GitLab using the GitHub enterprise connector:

Edited Apr 20, 2023 by Luke Duncalfe