Ok, I ll try to do this. 2011/4/23 Michael MacFadden <michael.macfad...@gmail.com>
> It would be good if some one could run the export script and take a look at > the CSV to see if there are any glaring mistakes. Thanks. > > ~Michael > > On Apr 23, 2011, at 10:28 AM, Yuri Z wrote: > > > Great Michael! > > Please let me know if you think I can assist with the Jira move. > > Yuri > > > > 2011/4/23 Michael MacFadden <michael.macfad...@gmail.com> > > > >> All, > >> > >> I have made significant enhancements to the issue export script which > >> should allow us to move the issues over. Here is what I did > >> > >> The id was shortened to simply the issue Id number from the url. > >> The columns were re-ordered and renamed to line up with how Jira > typically > >> orders them. > >> The comments from the google code issue were moved from the description > to > >> a single comment column. This way the comments will appear as a single > >> comment in the Jira issue. > >> The handling of the labels was enhanced to specifically look for the > >> priority and type labels using string parsing. > >> The column values for Priority and Type are now mapped from the Google > Code > >> statuses to the corresponding Jira values. > >> Google Code only has the concept of status, where as Jira has both a > status > >> (open/closed) and a resolution (fixed, duplicate, etc). The single > Google > >> Code status is now mapped to two columns in the export representing > status > >> and resolution. > >> General code cleanup and commenting. > >> > >> > >> As Christian pointed out, the comments and description contain some > HTML. > >> This shouldn't hurt Jira, it will just be treated as text. For open > issues > >> there might be some manual clean up of text required if anyone cares. > >> > >> > >> ~Michael > >
