The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
| Stage | Foundations |
| Maturity | Viable |
| Content Last Reviewed | 2025-04-07 |
Thanks for visiting this category direction page on Integrations in GitLab. This page belongs to the Import and Integrate group of the Foundations stage and is maintained by the group's Product Manager, Magdalena Frankiewicz (E-mail, Calendly).
This direction page is a work in progress, and everyone can contribute:
GitLab's vision is to be the best single application for every part of the DevOps toolchain. However, we acknowledge that to achieve this, there are many workflows, custom scripts, and nuanced integrations that customers require and GitLab may not be able to prioritize. To make the most impact and keep the Integrations category sustainable, we have been focusing on improvements to the technical foundations of integrations as well as documentation, guides, and best practices to assist the broader community in contributing to integrations. For FY26, the Import and Integrate team will be focusing primarily on improving migration capabilities between GitLab instances and from third-party tools to GitLab. Due to resource constraints and alignment with company objectives, we have deprioritized active development of integrations for this fiscal year.
For FY26, the Import and Integrate team is prioritizing Importers Category:
These priorities align with GitLab's company objectives.
We will continue to maintain existing integrations to ensure they remain functional, but we will not be actively developing new features for integrations during FY26. This approach allows us to focus our resources on migration capabilities while ensuring that existing integrations continue to work as expected. Our popular integrations like GitLab for Slack and Jira integrations will be maintained, but new feature development is currently on hold.
We continue to work to shift responsibilities as DRIs of integrations to individual product teams within the domain areas across GitLab. This gives groups full visibility and ownership in serving customers in their domains, based on each group's comprehensive strategy. This also helps to make the Integration category more sustainable. Group Import and Integrate maintains ownership of the foundations of integrations and the Integration development guidelines. We continue to offer guidance on integration best practices to anyone who contributes.
As we work to better define ownership of integrations across GitLab, the list below clarifies the current ownership of maintenance, security, and new feature development of each integration.
Security related integrations, owned by group Anti-Abuse:
CI/CD integrations, owned by group Pipeline Execution:
Integrations owned by group Project Management:
Integrations owned by group Source Code:
Integrations owned by group Incubation:
Integrations owner by group Container Registry:
Elasticsearch integration is owned by group Global Search.
Datadog integration is owned by group Runner.
Gitpod integration is owned by group IDE.
Google Cloud IAM integration is owned by group Authentication.
Packagist is owned by group Package Registry.
Visual Studio Code extension is owned by group Editor Extensions.
External issue trackers, ownership negotiated with group Project Management, currently maintained by group Import and Integrate:
"Notification" integrations, maintained by group Import and Integrate:
Other integrations, currently maintained by group Import and Integrate:
While a marketplace for GitLab integrations and extensions could provide significant value in the future, it has been deprioritized for FY26. Our strategic brief considers this as a potential longer-term initiative, but current resource constraints prevent us from pursuing it at this time.
Although enhancing these integrations would support customer retention and satisfaction, we have deprioritized these improvements for FY26 to focus on migration capabilities.
Import and Integrate group won't focus on developing new integrations, but we will continue to support other GitLab product groups, partners, and Community contributors in doing that.
In the longer term, we recognize the potential value of:
These initiatives, while valuable, have been deprioritized for FY26 due to resource constraints and the need to focus on high-impact migration capabilities.
If you want to contribute to an existing integrations, you can look for open issues labelled with this integration name, e.g "Integration::Asana" or "Integration::Jira".
If you'd like to contribute a new integration, please first review Integration development guidelines. Contact GitLab group owning the domain the new integration fits best, so that the group is aware of the planned contribution. Import and Integrate offers guidance on integrations best practices during development, by reviewing MRs and answering technical questions.
If you're interested in general Integrations area, you can find open issues with ~"Category:Integrations" label, however this list contains issues specific to particular integrations as well.
Feel free to reach out to the team directly if you need guidance or want feedback on your work by using the ~"group::import and integrate" label on your open merge requests.
You can read more about our general contribution guidelines here.
If your company is interested in partnering with GitLab, check out the GitLab Partner Program page for more info.
