Define a plan for Deprecating the Jira GitHub Enterprise DVCS Connector
Partner communications
Dec 6, 2022
: "May 23 is the last time when Atlassian customers can migrate off."
May 10, 2022
: "We are going to work on a deprecation plan soon for DVCS. The rough timeline I can tell you right now is that you should work towards delivering a new solution by around June, adding self-managed support to the Connect app. Then we can work on migrating customers to the new integration. We’re hoping everyone will be off the DVCS connector by later this year and we will delete the code early next year."
This issue is intended for discussion/identification of any gaps/dependencies required to give existing users a path off the connector.
Current State of Jira Integrations
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
Feature Gap Analysis across Jira Integrations
Active Usage
We appear to have 23 Self-managed instances and 3346 GitLab.com projects still actively using Jira Cloud DVCS.
For comparison, there are 415k projects using the Jira Server DVCS integration compared to 4.9k using the Jira Cloud DVCS integration (in Aug 2022).
If we complete the Jira Proxy release in %15.7 (releasing on Dec 22), that gives customers five months to migrate off of Jira Cloud DVCS to the GitLab for Jira app before a %16.0 removal.
The Plan
-
Complete Jira Proxy for Self-managed users (GitLab for Jira App) -
Create blog post discussing the new Jira proxy solution, the deprecation, and options for migration -
Identify impacted customers (both GitLab.com and Self-managed) -
Work with Atlassian to identify channels for communicating on their end -
Determine a communication plan on our end for reaching out to individual customers who require migration -
Migration guide? -
Identify any gaps, scripts, bugs, or enhancements that could ease the migration process and adoption of the GitLab for Jira app