4 ms·

Show HN: Jira to Gitlab Issue Migration Tool

26 points by wingmanjd 4y ago

$DAYJOB needed to migrate from JIRA to Gitlab due to business reasons (not related to the recent outage), so I wrote this issue migration tool [1] to help us preserve our historical data. This tool will copy issues from various JIRA projects to mirrored Gitlab projects (e.g. A jira project named JIRA-PROJECT1 will have its issues migrated to a gitlab project GL-PROJECT1). The tool also migrates issue comments to Gitlab notes and will recreate the existing issue links. YMMV, but this is working well for us. Comments welcomed. 1: https://gitlab.com/jeremygonyea/jira-to-gitlab-miigration-tool

searchableguy 4y ago
If I were gitlab, I would sponsor this project and promote it.
mihaigalos 4y ago
Is Jira still a thing in modern SW development?
- fire 4y ago
  unfortunately
- wingmanjd 4y ago
  I feel like my experience with JIRA across two organizations wasn't as bad as many (most?) others have experienced. Neither place used it heavily for management reporting, but mostly as a developer-centered tool to help with tracking issues, sprints, etc. with some very light workflow management. To that end, I found JIRA to work well enough for the needs we had at the time.
throwaway69123 4y ago
I wish there were more two way sync tools so we could choose what ever tool worked at the time
spdustin 4y ago
I wish this existed for Asana. FYI: a use case that’s near and dear to me is agencies working with clients that prefer to use their own task management tools to post issues/requests. We live in Gitlab, but clients love their own tools; asking them to use Gitlab for issues (even via email to service desk) is too much friction.
- wingmanjd 4y ago
  Which way would you import/ export? I'm already going to be investigating/ writing a Gitlab.com to some local copy for offline backups (the recent JIRA outage has us a little nervous putting all the eggs into one basket that someone else is holding).
  - spdustin 4y ago
    Asana -> Gitlab is a good start; two-way sync is ideal. We've cobbled together a number of Zaps on Zapier as a prototype, and I've been writing up a quick NodeJS sync between them.

26 points by wingmanjd 4y ago

searchableguy 4y ago

If I were gitlab, I would sponsor this project and promote it.

mihaigalos 4y ago

Is Jira still a thing in modern SW development?

fire 4y ago
unfortunately
wingmanjd 4y ago
I feel like my experience with JIRA across two organizations wasn't as bad as many (most?) others have experienced. Neither place used it heavily for management reporting, but mostly as a developer-centered tool to help with tracking issues, sprints, etc. with some very light workflow management. To that end, I found JIRA to work well enough for the needs we had at the time.

throwaway69123 4y ago

I wish there were more two way sync tools so we could choose what ever tool worked at the time

spdustin 4y ago

I wish this existed for Asana. FYI: a use case that’s near and dear to me is agencies working with clients that prefer to use their own task management tools to post issues/requests. We live in Gitlab, but clients love their own tools; asking them to use Gitlab for issues (even via email to service desk) is too much friction.

wingmanjd 4y ago
Which way would you import/ export? I'm already going to be investigating/ writing a Gitlab.com to some local copy for offline backups (the recent JIRA outage has us a little nervous putting all the eggs into one basket that someone else is holding).
- spdustin 4y ago
  Asana -> Gitlab is a good start; two-way sync is ideal. We've cobbled together a number of Zaps on Zapier as a prototype, and I've been writing up a quick NodeJS sync between them.