GitLab JIRA Integration
Ensure developers in GitLab and project managers in JIRA remain in tune
DocumentationBetter JIRA integration than Atlassian
GitLab is an integrated application from planning to monitoring with GitLab issues being a powerful tool for idea management, iteration planning, issue tracking and software development.
However, we recognize that many organizations have been using JIRA for many years and have existing data and business processes built into it. Our goal is to make GitLab work seamlessly with JIRA, offer the best integration possible, better than the current Atlassian suite provides.
If and when you are ready to migrate to GitLab issues, we provide the tools and practices to help you with that.
See below for our current integration features and future plans.
Integrate JIRA with GitLab merge requests
If you want to continue using JIRA, we got you covered. Here's a short list of what you can do when integrating GitLab with JIRA.
- One GitLab project integrates with all the JIRA projects in a single JIRA instance.
- Quickly navigate to JIRA issues from GitLab.
- Detect and link to JIRA issues from GitLab commits and merge requests.
- Log GitLab events in the associated JIRA issue.
- Automatically close (transition) JIRA issues with GitLab commits and merge requests.
- Learn more in our JIRA integration docs
Migrate from JIRA to GitLab issues
Have you used GitLab issues before? We offer a lot of great functionality that is comparable to JIRA or even better!
- Issue Boards can be used in place of the Agile feature of JIRA. If you use Scrum, GitLab Issue Boards will be a nice fit.
- Related issues are a bi-directional relationship between any two issues and appear in a block below the issue description. Issues can be across groups and projects.
- Milestones allow you to organize issues and merge requests into a cohesive group, optionally setting a start and a due date. They are a valuable tool to track the development of the process of achieving a goal.
- Burndown Charts can be used to see the current state for the completion a given milestone in a clear and beautiful chart.
- Due dates can be used in issues to keep track of deadlines and make sure features are shipped on time.
- Adding a weight to each issue you can get a better idea of how much time, value or complexity a given issue has or will cost. This is particularly useful when you have a lot of issues, where it can be hard to get an overview.
Upcoming features
We're constantly working on improving GitLab's integration with JIRA. Here's a list of features we're considering implementing.
GitLab Community Edition
- Import JIRA issues CSV export into GitLab issues: Make it easier to migrate from Jira. Subscribe to issue
GitLab Enterprise Edition Premium
- Import JIRA project issues into GitLab project issues: switch from JIRA to GitLab as your ticketing system. Subscribe to issue
- Automatic and multiple type JIRA issue transitions: Transition the state of a JIRA ticket multiple times depending on the status/workflow in GitLab. Subscribe to issue
- GitLab group level integration: for instances that make use of groups, support JIRA at the group level as well. Subscribe to issue
- GitLab instance level integration: define credentials for JIRA integration on a system level, so that unnecessary round-trips to Ops from developers could be avoided. Subscribe to issue
- JIRA transitions for non-default GitLab branches: Extend the functionality of the issue closing pattern on branches other than the default. Subscribe to issue
