Importing data from Redmine

The Jira Redmine Importer plugin allows you to import data from the Redmine Issue Tracker application into your local Jira instance. Version 5.0.2 or later of the Jira Importers Plugin is compatible with Redmine versions 1.3.0+ and 2.5.2.

Before you begin

  • Ensure that you are using Redmine versions 1.3.0+ and 2.5.2.
  • Ensure that you are using version 5.0.2 or later of the Jira Importers Plugin. This plugin is bundled with Jira. For instructions on how to update a plugin, see Updating apps.
  • Install the Jira Redmine Importer plugin, if you haven't installed it already. For instructions on how to install a plugin, see Installing Marketplace apps.
  • Enable the REST web service in Redmine in Administration > Settings > Authentication > Enable REST web service, if you haven't already enabled it.
  • If your Jira installation has existing data, back up your existing Jira data.

  • (tick) Tip: Redmine supports hierarchical issues. In the Redmine Import Wizard, you are given the option to recreate this issue hierarchy through Jira issue links. Therefore, before importing Redmine data, you may want to configure a custom issue link to replicate this hierarchy. For example:

    • Name — 'Hierarchy'
    • Outward Link Description — 'parent of'
    • Inward Link Description — 'child of'

Import your Redmine data

The Jira Redmine Importer plugin provides a wizard that walks you through the process of importing data and integrating it with Jira. To access the import wizard:

  1. Log into Jira as a user with the Jira Administrators global permission.
  2. Choose > System. Select Import & Export > External System Import to open the Import external projects page. 
  3. Select Redmine to open the Redmine import wizard.
  4. Complete the fields as prompted in the wizard. 

If you are importing your Redmine issues into an existing Jira project, you must choose the Jira workflow scheme used by that existing Jira project when you are prompted to select the workflow scheme. Otherwise, your import may not complete successfully.

Please note that it is mandatory to map Redmine status field to a specific Jira status field and Redmine tracker field to a Jira issue type field since these Jira fields are an integral part of Jira workflows.

Tips for importing Redmine On Demand data into Jira fields

The import process converts Redmine data as follows:

In Redmine

In Jira

Import Notes



Redmine data is imported on a per-project basis. You can either specify an existing Jira project as the target, or the importer will automatically create a project(s) for you at time of import. See Defining a project for more information about Jira projects.

Target Version

Affects VersionRedmine target version is mapped to Jira "affects version".



You can configure mapping of specific Redmine values to specific Jira values.



Redmine subject is imported as the Jira issue summary.

WorklogWorklogSee Configuring time tracking.
AuthorReporterRedmine issue author is mapped as Jira Issue Reporter.



Attachments are extracted from Redmine and saved. Information on the date the file was attached and the user who attached it is retained, as well. To specify the location where the attachments are stored, see Configuring file attachments.


Issue Type

You can configure the mapping of specific trackers to specific Jira issue types.



You can configure the mapping of specific Redmine values to specific Jira values.



You can configure the mapping of specific Redmine values to specific Jira values, provided you create your workflows in Jira before running the importer.

  • The Jira status field is integral to Jira workflow.d
  • To create a Jira workflow, see Working with workflows.
  • To create a Jira workflow scheme (which you can then associate with appropriate projects and Issue Types), see Managing your workflows.
CategoryComponent/sThis mapping is hard-coded and cannot be changed.



Jira will automatically import all users from Redmine, unless you are using external user management, in which case Jira will not import any users. Jira will then try to work out if the users are required, for example if the user has made a comment, or reported an issue. If the users are not required, Jira will add them to a group called redmine-import-unused-users, and you can then decide what you'd like to do with these users (you may decide to delete or deactivate them).

Other fields

Custom fields

If your Redmine system contains any custom fields, you can choose to map them to specific Jira custom field(s). If your custom fields don't yet exist in Jira, the importer can automatically create them for you.

Last modified on Mar 26, 2019

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.