Migrating your JIRA issues to GitLab

Linagora, a strong proponent of open-source solutions, recently migrated from Atlassian's JIRA and Bitbucket to GitLab, aiming to fully utilize GitLab as their sole open-source development tool. The migration from Bitbucket was straightforward due to Git's capabilities, but transferring JIRA issues to GitLab presented challenges due to the lack of a native migration tool, leading them to rely on REST API calls. The process involves gathering necessary information from both JIRA and GitLab, using a preferred HTTP client like Axios, and mapping JIRA issue fields to GitLab's format, including user assignments and comments. The migration strategy ensures that even if JIRA users do not exist in GitLab, they can still be mapped using a GitLab token. This approach allows developers to perform daily REST API calls to facilitate seamless issue migration, aligning with Linagora's open-source philosophy and their invitation to new talents to join their team.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.