Learn more about our GitLab + Jira integration, including what fields are synced between the two tools, and your customization options.Bitbucket isn’t the only Git solution that can play nicely with Jira anymore. With Unito, you can seamlessly use Jira for your issue tracking and GitLab for version control. Here's how these two tools come together with Unito.
What is synced?
See a field you would like to sync that’s not listed? Contact us - we may already support it through a manual configuration.
What is not synced?
GitLab Merge Requests: On the roadmap.
GitLab Priority: On the roadmap.
Jira Sprints: Currently, these are read-only; supporting two-way syncing with them is on our roadmap.
Jira links and dependencies: On the roadmap.
Jira time tracking: On the roadmap.
Mentions: Unito does not support user mentions in titles, descriptions, or comments just yet, but this is coming soon.
Is there a feature you would really like? Contact us! We prioritize based on user requests.
Here are all the available options for Jira and GitLab:
Filter synced work items
Unito will sync all items by default but you can customize your workflow by syncing just some of them (complete guide).
Filter by issue type
You can filter which type of issues you want to be synced to Jira (complete guide).
You can choose to sync only from GitLab to Jira or Jira to GitLab. Here is how it works.
Map your Jira and GitLab users
Here is a complete article on how to sync teammates.
Sync closed items
Unito will automatically sync open items automatically. But here is how you can sync closed items.
Prefix item title with Jira/Gitlab issue number
Unito doesn't sync the issue number by default but you can enable that (for either Jira or GitLab) in your flow settings. Here is how to do it.
Default type for new Jira issues
You can choose which type of issue should be created by default in Jira when a new issue is created in GitLab.