exporting full ticket data in csv

Steve Smith's Avatar

Steve Smith

17 Nov, 2010 05:31 PM

One of the projects we're working on requires us to use a different issue tracking system, so I would like to export all the ticket info for that project into csv so that I can import it into the other system. As others have noted, exporting from the tickets tab only exports a summary of the bugs, not the full bug information. The only other solution I've found is to export all of our account data, which I have done. Unfortunately, this isn't much help. First, each individual ticket has its own export files for csv and json. Second, as far as I can tell, the csv that is generated is incomplete and, ironically enough, has no commas at all. I'm at a loss as to how I'm going to migrate my issues to the other system. Any suggestions?

  1. 1 Posted by Justin Palmer on 17 Nov, 2010 07:05 PM

    Justin Palmer's Avatar

    It should be fairly easy to combine the json files and/or import them even though they are in separate directories. The reason the CSV files don't contain ticket comments is because they share some of the same and some different headers than the ticket itself.

    In Ruby, this would look something like code below:

    require 'rubygems'
    require 'json'
    
    Dir['export_dir/project_dir/**/ticket.json'].each do |f|
      ticket = JSON.parse(File.read(f))
      ## Do import/manipulation here
    end
  2. Nicole closed this discussion on 20 Dec, 2010 04:00 PM.

Discussions are closed to public comments.
If you need help with Lighthouse please start a new discussion.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac