Are you planning to move the redmine issues to JIRA ?

Ways to merge Issues from Redmine to JIRA.

Using JSON
Using CSV
Using Plugin
Merging is tough if you are moving from Redmine to JIRA. One has to compromise with many things while moving from Redmine to JIRA.

Things one has to Compromises:

1. Redmine is free but JIRA comes with a cost.
2. You may lose historical information about the project.
3. For summary type tasks there is no assignee field. it will go as unassigned in JIRA after migration.
4. If the user left the organization and JIRA is not having details by default it shows blank or importer details.
5. Text formatting won’t be the same.
6. There is no background color for the sentence.
7. While importing JIRA creates a “custom field” make sure you run first migration on test setup or delete the old custom fields manually before it gets flooded.
8. You can not have the same issue id on JIRA. JIRA will create a new issue id while migrating.
9. You may lose external linkage with issue id. Suppose one has an issue history where issue id was used to check-in code in git. It will be difficult to keep the same record.
10. There is no subproject in JIRA.
11. You may see attachment errors.
12. You may lose links to the Redmine wiki.

If you still planning to move to JIRA. There could be some workarounds for the above problems.

1. Use a plugin to migrate the issue or use the redmine2Jira python package to import.
2. Create a script that will validate all the fields in JIRA post-migration.
3. The script may not help so you have to go through multiple review processes to find out all the problems.
4. Before importing create a bot user “Importer” and let it do the migration work.
5. For a few issues there will be not assignee and reporter, You can create a custom field as an original reporter and original assignee and update the field using rest API.
6. See the Macros available in Redmine and corresponding macros for JIRA. Run the script and replace that on JIRA.
7. For the subproject, one can use component features in JIRA.
8. You can map the Redmine Issue ID as an external Issue ID on JIRA.

Recommendations:

• Maintain Redmine but start afresh in JIRA – With your required workflow design while migration, you may impose Redmine features to JIRA and limiting yourself to explore the complete feature of JIRA so this will be best if you start fresh in JIRA.
• Keep the Redmine old issues in JIRA just for history – One can migrate the issues following the above workaround but keep that as an old project just for history purpose and completely get rid of Redmine.
• Migrate the issues if you completely understand the mapping between Redmine and JIRA – For example, Summary Task can be mapped as EPIC in JIRA and author in Redmine as a reporter in JIRA.
• Agile board design – Understand your project requirement and follow the correct board.