Importing data from Bitbucket

The Jira Bitbucket Importer plugin allows you to import data from Bitbucket into your local Jira instance.

Before you begin

(warning) Note: For all of the following procedures, you must be logged in as a user with the Jira Administrators global permission.

Import your Bitbucket data

The Jira Bitbucket Importer plugin provides a wizard that walks you through the process of importing data and integrating it with Jira. After you've installed it, run the wizard to import your Bitbucket data:

  1. Choose > System
  2.  In the Import & Export section, select Bitbucket.
  3. Complete the fields as prompted in the wizard. Depending on how your sites are configured, you might be redirected to Bitbucket in order to set the authorization needed to export data.

If you are importing Bitbucket 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.

In addition, you must map Bitbucket statuses to Jira statuses in order for Jira workflows to work with the issues.

Tips for importing Bitbucket data into Jira fields

The import process converts Bitbucket data as follows:

In Bitbucket

In Jira

Import Notes



Bitbucket 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 one or more projects during the import. See Defining a project for more information about Jira projects.



Bitbucket subject is imported as the Jira issue summary.

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



Attachments are extracted from Bitbucket 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 kinds to specific Jira issue types.



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



You can configure the mapping of specific Bitbucket 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.
  • 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.



You can choose to have the importer automatically create Jira users for any Bitbucket users who do not already exist in Jira.

  • Users who interacted with the Bitbucket system will be created as active accounts in Jira. Other users will be imported into a special group called "bitbucket-import-unused-users" and will be deactivated.
  • Passwords from Bitbucket are not imported. Users from Bitbucket must have their passwords emailed to them the first time they log into Jira.
  • If you are using External User Management, the import process will not be able to create Jira users; instead, the importer will give you a list of any new users that need to be created. You will need to create the users in your external user repository before starting the import.
  • If you have a user-limited license (e.g. personal license), and the number of required users is larger than the limit, then the import will be stopped. A page will open and list the users that can't be created.
Last modified on May 20, 2019

Was this helpful?

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