You can also create a jelly script and either past it into the JIRA web interface or point JIRA at a file on the JIRA server that contains the script. I've use this to import both comments and attachments.
-Tad On Wed, Apr 6, 2011 at 9:23 PM, Michael MacFadden < michael.macfad...@gmail.com> wrote: > Ok, I need to circle back with the infra guys to see how comments are > imported. There might be a way to build out this script that would make the > import easier, if they can tell me the proper import format. > > ~Michael > > On Apr 6, 2011, at 8:40 PM, Soren Lassen wrote: > > > FYI, James Purser has written a script: > > > > http://code.google.com/p/wave-protocol/source/browse/issue_exporter.py > > > > which exports the code.google.com/p/wave-protocol issues in a CSV, but > > there are some important unresolved shortcomings, including that it > > doesn't capture comments, as you say. See the TODOs in the script. All > > improvements to the script are very welcome. > > > > Soren > > > > On Thu, Apr 7, 2011 at 1:21 PM, Michael MacFadden > > <michael.macfad...@gmail.com> wrote: > >> All, > >> > >> I am working with the infra crew to get our Jira issues ported over. > The way we do this is to basically give them a CSV of the current issues. > The question is what do we want to export exactly from the google code > project and does anyone know how we can export them. > >> > >> From the issue list it looks like you can get a CSV, but I don't think > that would capture things like comments inside the issue. > >> > >> Any ideas? > >> > >> ~Michael > >
