1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues


Issue #232 resolved

Add ability to export/import issues (BB-1473)

Chris Rebert
created an issue

Comments (80)

  1. Martin Geisler

    We have recently discussed using Bitbucket in a company I'm involved in, and the lack of an export function concerned people.

    I don't think it's a big deal, but others were afraid that the tracker data would become inaccessible if Bitbucket were to disappear one day.

  2. Mike Lissner

    Just commenting to say that on a project I have, there are about 100 open bugs, and prioritizing them within bitbucket is challenging. We'd love to export them so we can figure them out in a spreadsheet.

  3. Priory

    +1 This is a feature sorely lacking. As the functionality in the issue tracker is pretty simple, the ability to export and then manipulate in excel etc is vital.

  4. Priory

    Further to my earlier comment that said you can use the API for this, unfortunately the API doesn't give you access to the issue comments, making it not possible to use this to export your issues from bitbucket.

  5. Martin Geisler

    Hi guys! I'm a Mercurial developer and as such I use Bitbucket a lot... Please contact me at mg@aragost.com if you would be interested in contracting with me to write an export tool for the Bitbucket issues.

    I know the Bitbucket API doesn't show comments and attachments yet, so we'll have to work around that with some screen-scraping for now.

  6. Rui

    +1, this would be huge differentiating factor vs other issue trackers. Recently in order to migrate a issues from GoogleCode to Bitbucket, I had to mix up some python to call the REST API and automate "part" of the process - the whole process I kept wishing there was more or less standard way to do it..

    Maybe it is time to create a Bitbucket' desktop app - to help with this kind of workflows. Anyone up for a chat on this?

  7. James Hitchcock


    I've just started writing a client to export and import issues using the API to various formats.

    I've written a basic exporter to export issues to CSV. You can download it from here: http://jhitchcock.com/?p=44

    I'll improve over the coming weeks / months so let me know if you want any features, and keep an eye on the blog !

  8. Pedro Gomez

    Wasn't this functionality already in about a year ago? I am almost positive I was able to export to CSV in the past. +1 from me as this helps organize with clients as well so they can see what is left, etc.

  9. Martin Geisler

    Please stop with the +1 comments — add yourself as a watcher instead!

    That way you avoid sending out emails to everybody else who watches the issue and you still show your interest it.

  10. Michael Eber

    I feel that this issue is much more than just a "nice-to-have". We are planning on using BitBucket for one of our development projects with a remote and local team. Our need for export is important: all issue tracking, and resolutions to the issues, must be provided to our auditors at the end of the year. To say "go look at bitbucket" is not a solution that an auditor wants to hear. Please consider raising this above a nice-to-have status.

  11. ndudenhoeffer NA

    Enough with the plus ones! Use the 'watch' feature to let the developers know this would help you. When you comment, everyone else who is watching get's an unnecessary email.

    On a side note, you can implement this using the Bitbucket API. There is a python implementation of the API available here.

  12. Kavi Sharma

    Thats interesting. The paid solution for BB issue tracking is JIRA, and there is no migration path available to move existing issues logged with BB. Thats a significant gap.

  13. John Conrad

    By posting useless comments you guys are reducing the visibility of this issue because it causes people to stop watching it. Every comment sends out an email. Stop commenting if you have nothing to add.

  14. Martin Geisler

    I think you should open new issues if you want to import issues from other formats. Personally, I think the solution implemented by Bitbucket is great: since there is no standard forward for importing/exporting issues across different systems, they defined an open standard. You can now write your own Excel-to-Bitbucket-issues converters as needed.

  15. brice.copy@cern.ch

    Don't get me wrong, I think a REST API is great, but a CSV import was all that's needed. Personnally I don't have the time to write an importer, so I'll wait until someone tackles that. (pardon my frustration, I was ousted when the ATLASSIAN DEV hosting service closed, and my project is currently homeless).

  16. Sam Johnson

    Wow, really disappointing response from BitBucket. User after user after user asked for an export function, so we could easily access downloads of issues data. What you instead gave us is your own data format - how is that an "export"?

    If you need to hire a programmer in order to get at the data, then it's not what 99% of people would call an "export".

    I'm begging here: please create a new issue ("Ability to transfer issues between BitBucket repositories"), attach your solution to that, and then please please please re-open this issue that everyone desperately wants resolved...

  17. Alexandru G

    Sam Johnson said:
    What you instead gave us is your own data format - how is that an "export"?

    What "own format" are you talking about ? Do you actually know a standardized data format for issues that exists ?

    For what I know there is no standard at the moment, so they gave us the data in a format that is easy for them.

  18. Erik Twee

    I'm begging here: please create a new issue ("Ability to transfer issues between BitBucket repositories"), attach your solution to that

    Sam Johnson Were you not able to click "export" on one repo and then upload that .zip file on the "import" of the other repo?

  19. Sam Johnson

    Hi Erik. Sure, but that's not "exporting" issues, that's moving them. This ticket is about being able to export them.

    Just to remind everyone what this issue is about, some of the earliest postings to this issue were:

    Just commenting to say that on a project I have, there are about 100 open bugs, and prioritizing them within bitbucket is challenging. We'd love to export them so we can figure them out in a spreadsheet

    I would really like to export issues, we wanted to move the open issues to dedicated bug tracking and now have to re-type them

    This is a feature sorely lacking. As the functionality in the issue tracker is pretty simple, the ability to export and then manipulate in excel etc is vital

    The functionality that was implemented isn't the "export" that hordes of people here have requested. PLEASE RE-OPEN THIS ISSUE UNTIL IT's TRULY RESOLVED!

  20. Erik van Zijst staff

    Sam Johnson You talk about a standardized issue export format. I'm not aware of any standard and so we drafted a format that is capable of storing Bitbucket issues.

    Or do you mean the actual file format, such as CSV? For a brief instant we considered using CSV instead of JSON, but CSV is actually not much of a standard. There are many slightly incompatible implementations out there that all have different ideas about escape characters, newlines, whether or not true numerical values exist and above all, unicode encoding.

    We ran into plenty of edge cases that would have made simple things rather complicated both for us as well as the person having to parse it and so we chose JSON.

    Also, CSV itself isn't able to deal with issue attachments.

    Anyway, even if we had picked CSV, you'd been able to load it into Excel and perform sophisticated manipulations, but you still wouldn't be able to "move the open issues to dedicated bug tracking" if by that you mean an issue tracker other than Bitbucket's, as there's no common standard.

    So to cut a long story short: CSV's lack of true standardization and various dialects actually makes it a suboptimal format for exporting arbitrary data.

    Now in case you don't care about 100% reversibility of the process (and I realize there are plenty of scenarios in which that might be the case), then you might be able to live with CSV.

    Challenge: maybe someone can do a quick script that turns the JSON into some CSV dialect compatible with Sam's needs?

  21. Drew Rhoades

    Erik van Zijst You are so missing the point. I don't need a format targeted at system integration. I need a format that is easily consumable for external tools, such as Excel (CSV works great). I have to track and report metrics about my issues trends, outstanding counts, etc. This sort of reporting in Bitbucket is meager, at best. The simplest, most flexible answer is to give me a basic "dump" of the issues so I can slice and dice them as I please. This even allows me to share the list of issues with people that don't have access to Bitbucket - another bonus.

    I really hope someone with a little extra time rises to your challenge, because it would relieve some friction in my status reporting process.

  22. Erik van Zijst staff

    Drew Rhoades Sam Johnson I'm happy to hack up a script when I have some time, but that does lead me to wonder exactly what you expect to see in a csv file.

    A csv file is just a two-dimensional array and can therefor only really capture 1 type of object. Each row can be an issue, but then where would comments go? Or the state change logs?

    Would you expect several separate csv files (issues, comments, logs), or do you not care about any of this data at all? What about other people? Is there an obvious solution that meets everybody's expectation?

    I'm happy help out, but our ideas about what "issues export" entails are indeed vastly different.

  23. XD Systems - Development

    if you don't mind working with MS Word :)

    a not so optimal solutions but try to: copy the issues table (you'll need to do that page by page) to a new word document. This automatically converts the copied HTML table to a word table. And then you can work with it.

  24. Samuel Haddad

    Can we reopen this issue? Currently you can export the issues, but not to something you can easily work with.

    Erik van Zijst did make a nice script, which might be ok for developers, but a project manager, might not be savvy enough to install python and run his script. I would love to be able to just export to a csv or xlsx and perform some analytics in Excel.

  25. Erik van Zijst staff

    Samuel Haddad This issue was about the ability to import and export issues between other issue trackers. Since that has been fixed, I suggest we keep this issue resolved.

    The issue about being able to load up a subset of issue data into Excel got mixed in later on, but IMHO is different. Please open a new issue for Excel to we can track and discuss it independently.

  26. Dan Merns

    I am trying to figure out how to do this with the new bitbucket responsive design but the old instructions no longer seem to apply. Does anyone have updated instructions?

  27. Log in to comment