This process requires the assistance of the DoIT Shared Tools team. Email st-help@doit.wisc.edu to start a new request. If you do not have an existing GitLab group and project, complete this needs analysis. The team will help you with both requests. 

When you import issues from Jira to GitLab the following issue fields will be included:

• Title
• Description
• Labels
• Assignee/Users

When Should You Import Jira Issues into GitLab?

• 50 issues or less: review your backlog, determine what to keep, and manually migrate epics and issues into GitLab
• More than 50 issues: consider importing the Jira issues and refining your backlog after an import

Tips for Managing your Import

Learn about Project Management in GitLab

Groups with specific requirements around Issue workflows may want to watch tutorials or attend a workshop on GitLab - Project Management and Service Desk.

Map users

You need to configure user mappings during your import process, in order for Issues to be assigned to the same user in GitLab as in Jira.  

Bulk Add Labels

Jira Labels will be imported with the Issues.  But if you find you need to add further Labels after the import, you can create your own Labels in GitLab and add them to many Issues at once in a bulk edit action.

Customize your Issue Board

GitLab Issue Boards offer customizations that may suit your use case.  If your group could benefit from a particular workflow, check the GitLab documentation on Issue board customization for the options available to you.  

For example, you can create your own Labels for Issue status and then build an Issue Board with a swimlane that filters for the Issues with each status.

Jira Import Video (2:41)

Jira Cloud

The information in this document is relevant importing from a self-hosted Jira instance, not from the Jira Cloud service.  If you'd like to import content from a Jira Cloud account to GitLab, contact the Shared Tools team (DoIT Shared Tools - Contact Us).

Related Resources

1. GitLab with Jira