The simple solution with a link back to the original Google Code issue
sounds OK to me.
We can keep the Google Code issues available for as long as we want. I
can't see a way to make the Google Code issues read-only but it should
be easy enough to communicate that new comments and new issues
If this can be done without too much trouble, I think it would also be
useful for links to the Jira bugs to be added to the Google Code issue
tracker (probably as comments) so people who come to comment on those bugs
know they have been moved.
—Zachary “Gamer_Z.” Yaro
On Apr 22, 2011 11:54 AM,
On Sat, Apr 23, 2011 at 01:32, Michael MacFadden
michael.macfad...@gmail.com wrote:
James has built a script (linked below) that is a good start, but dosn't as
of yet grab the comments.
I just fixed this (and some other problems with the script). It now
exports the comments as part of the
Thanks Christian. I will take a look at it. In regards to the assertion, it
looks like we are assuming only two labels for type and priority. Obviously an
issue can have other labels. This shouldn't be to hard to fix with some string
parsing instead of just assuming the number and position
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:
Right,
The trick is you can only do that if you are a JIRA admin, which we are not.
The infrastructure guys will have to do it, so it's really up to them on how
they want the data.
~Michael
On Apr 7, 2011, at 1:52 PM, Tad Glines wrote:
You can also create a jelly script and either past it
As far as I can remember, comments cannot be imported using CSV, so jelly is
the only bulk import option available.
-Tad
On Thu, Apr 7, 2011 at 2:56 PM, Michael MacFadden
michael.macfad...@gmail.com wrote:
Right,
The trick is you can only do that if you are a JIRA admin, which we are
not.
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
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
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
10 matches
Mail list logo
