Skip to end of metadata
Go to start of metadata

Repository administrators can export issues out of or import issues into a Bitbucket issue tracker.  The feature is useful for moving issues between two repositories.  You can export issues from one repo and into another.  Importing issues destroys existing issues in the tracker.

You cannot "undo" an import.  For this reason, it is a good idea to use the export function to backup an issue tracker before importing.

The import feature expects a ZIP file in the correct format. If you are moving issues between Bitbucket repositories, the export feature automatically produces the correct format. 

It is possible to write a utility to import data from other issue trackers.  Or, you can write a utility that transforms exported Bitbucket issues for import into another company's issue tracker.   Writing either utility would require that you understand the Issue Import/Export Data Format

How to Import 

You can import any ZIP file Log into Bitbucket using an account with administrative access to the repository. Then, do the following:

  1. Press the repository settings   icon.
    The repository settings page appears. 
  2. Select the Import & Export link from the left-hand navigation.
  3. Choose an archive file to upload.
  4. Press Start import.
    The system displays the import progress. 

    Some Mac OS, and other UNIX based systems, require the following for a successful import

     Ensure that the db-1.0.json file is at the root of the archive, and that any subfolders are also in the root. Generally this is done using the following:

     

     

How to Export 

Log into Bitbucket using an account with administrative access to the repository. Then, do the following:

  1. Press the repository settings   icon.
    The repository settings page appears. 
  2. Select the Import & Export link from the left-hand navigation.
  3. Press Start export.
    The system displays the export progress. When the exports completes, the system displays a dialog with a download link. 
  4. Download the completed zip file.
    The system also sends an email notification containing a link to the download file. 

4 Comments

  1. Anonymous

    For those looking to import or sync issues with Redmine, I wrote a script to do that:

    https://bitbucket.org/theasci/redmine-issues-to-bitbucket

    The script reads all the issues from Redmine's API and generates a ZIP file for each project that can be imported into Bitbucket. It also supports preserving existing issues in Bitbucket by using the export functionality.

  2. For Mantis to Bitbucket I wrote a script to do that:

    https://github.com/timotei/mantis-to-bitbucket-issues

    Or alternative repo on bitbucket: https://bitbucket.org/cegui/mantis-to-bitbucket-issues

  3. Is this still present? I see recently updated importers on GitHub for various X to Bitbucket migrations but I can't find the setting in the menu.

    1. I now know my mistake. I need to enable the issue tracker!