Due to a project name change, we'd like to start using a new Google Code project page, but as GC does not support renames, we need to migrate all the data manually. Most of it is easy, but the Issues are trickier. Google provides a Data API for them, and in fact I can get all the issues and their comments easily as XML with simple anonymous GET request.
I'd like to know how can I push this XML to the new project.
I can get as far as authenticating to the API and trying to push the XML, but I receive an error:
[Line 1, Column 249] Invalid root element, expected (http://www.w3.org/2005/Atom:entry), got (http://www.w3.org/2005/Atom:feed
So it doesn't accept the XML as is. I could separate all the
<entry> elements and push them one by one, but that sounds like a lot of work and very clunky. Isn't there a way to push multiple issues at once? Are there any other ways to migrate Google Code Issues?
I ended up writing a script for separating the issue XML entries for me, and managed to upload them, but sadly the IDs of the issues went wrong and more importantly, the reporter of all of the issues changed to me. Also, comments need to be handled separately, and it looks like I need to download the list for each issue, process those to separate the comments and then upload individually, probably with some funny effects like me being the commenter in every comment. So is the conclusion that Google Code Issues cannot be migrated with good results? Please tell me I'm wrong.