POC Jira Server importer

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Work on this issue
• Close this issue

This issue was created from Jira importer - technical evaluation (#438273 - closed).

What Jira importer should be capable of

The high-level details of what the Jira Importer should be capable of where noted in here. Repeating here:

1. Issue import improvements part 1 (for DataCenter and other versions later) - This would satisfy a vanilla import use case for issues
   • Comments
   • Attachments
   • Status as a label - Allow mapping to an existing label
   • Issue relationships (blocking, blocked, related)
   • Retain link to GitLab MRs
   • Custom fields in the issue description
   • Jira subtasks to GitLab tasks (maintain the relationship)
2. Epic import - This iteration would create a viable import experience.
   • Epics as epics (instead of issues with a label)
   • Issue relationships to epics
3. Issue import part 2 - These items would be nice-to-haves
   • Time tracking import
   • Links
   • Mapping of custom fields to individual labels
   • Component as a label
   • Priority as a label
   • Resolution as a label
   • Fix_version as a milestone
4. Out of scope
   • Mapping milestones/iterations to sprints - Mapping dates across both systems would be very difficult.

Importing chosen projects data from Jira to GitLab is expected to be a one-off process.

Jira2Lab by Professional Services

Professional Services developed a Python tool for migrating from Jira Server to GitLab, off of an open source project, called Jira2Lab. They will be open sourcing their project soon.

This tool and learnings from its implementation should be investigated here. Hopefully the tool can inform the implementation of Jira Server importer in the Product.

Goal of the POC

The aim is this POC would be to follow up on Jira importer - technical evaluation (#438273 - closed) and have a working POC that lets us:

1. understand the amount of work needed to deliver importer
2. discover difficulties early
3. get answers to doubts before begin of implementation starts
4. think about where components could be used (importer framework).

The result of this issue should be to add issues to the Jira Server importer (&13697) epic.