Move Jira integrations to Plan stage
What does this MR do and why?
This MR is to move the ownership of Jira integrations from groupimport and integrate to Plan stage, group to be decided by Plan stage.
This is based on the discussions and decisions takes during Product offsite, that took place end of April 2024.
groupimport and integrate is stopping further work on Jira integrations this month, after having completed the delivery of JIRA Issue Integration - Allow Multiple Project... (&12609 - closed). This was decided so that we have capacity to pick up implementation of Jira importer. This has been documented on Integrations direction page.
Below the description and data on two Jira integrations that GL maintains:
- Jira issue integration - also used to called basic Jira integration - this one works with all Jira types (Cloud, Server, Data Center) and allows for managing Jira issues from GitLab, like cross-referencing Jira issues and GitLab MRs, as well as viewing Jira issues in GitLab (Premium feature)
- GitLab for Jira Cloud app - work only with Jira Cloud, shows GitLab dev information in Jira in Jira development panel.
Usage statistics: Tableau link with Jira metrics; in short about 700000 projects used Jira integration in Feb'24.
Both integrations are in active use, there's many customer labelled feature requests and bugs.
All open issues labelled IntegrationJira 198.
JiraIssue integration In total 65 open issues. 16 bugs, including 9 bugs with SLO missed, and 9 bugs with customer label
JiraGitLab for Jira Cloud app In total 68 open issues. 17 bugs, including 6 bugs with SLO missed and 11 bugs with customer label
IntegrationJira without more specific JiraIssue integration or JiraGitLab for Jira Cloud app open issues 65. They are mostly feature requests, some maintenance issues.
Urgent requests: This feature Support individual user credentials for Jira in... (&4954) and this Add ability to create Merge request/branch from... (#326262) has been requested by Ultimate Prospect with 2500 seats, the first one was planned for Q2. More context on Prospect request here.
There's currently 1 Requests for Help related to Jira integration open. There's quite a few closed. This additionally speaks about customer interest in Jira integrations and also related workload.
What Import and Integrate group will still deliver
- It's been refined, implementation outlined and weighted about ~10 weight by group engineer here.
- Scope of the epic for clarified and adjusted: &4954 (comment 1880732647).
- I've reached out on Slack to Customer Success to understand the importance of implementing Support individual user credentials for Jira in... (&4954) for the business: if there's more interest then already been logged and how important this is. Result, another large Ultimate customer is highly interested in this.
As this was originally planned for Q2 (last year), it's an urgent request and it's been refined by groupimport and integrate engineer already, our group will still deliver it in Q2. The trade off to consider is that implementation of Jira importer will be pushed accordingly to capacity used up for implementing this feature.
- Ensure branches deleted in GitLab are deleted i... (#351625 - closed)
- JiraConnect: create branch sends to gitlab.com ... (#391432 - closed)
- GitLab for Jira app: Internal/developer technic... (#440730)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.