asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ian Maxon <>
Subject Re: Migration of issues to JIRA
Date Thu, 02 Jul 2015 19:57:07 GMT
To update, I was able to convert the issues into (what I believe to
be) a JSON object that JIRA should be able to load last week. We're
still blocked on hearing from Infrastructure though, as to whether or
not this exported data is OK or if it needs some tweaking. Any advice
on how to push this forward would be much appreciated.

- Ian

On Sat, Jun 13, 2015 at 2:42 AM, Jochen Wiedmann
<> wrote:
> Reading through the issues, the only offer made by infra was to follow
> So, I'd suggest that anyone does the export from Google Code and
> converts the data into the format as outlined there. Afterwards a new
> issue could be opened to import the result.
> And, additionally: I definitely would discourage any attempt to run
> the import for yourself. I'd hope that Infra provides the ability to
> have a test run, or the like, which mere users can't do.
> Jochen
> On Sat, Jun 13, 2015 at 10:04 AM, Mike Carey <> wrote:
>> Hopefully our mentors can help us quickly find a workable path? :-)
>> On 6/12/15 7:13 PM, Ian Maxon wrote:
>>> Hi all,
>>> So there has been a JIRA issue open for about a month now about
>>> migrating our issues from Google code to JIRA:
>>> . Not a lot of
>>> progress has been made on it unfortunately. It is becoming somewhat of
>>> a blocker. We would really like to be able to point people at our JIRA
>>> instance, rather than having to keep limping along with Google Code
>>> issues. I feel like having our activity shown on the JIRA instance
>>> will also make a lot of the work that goes on semi-internally already
>>> more visible to the community. There's also the fact that Google Code
>>> will be read-only in a matter of a few months (8/24).
>>> I see two ways forward with this. One is that we convert the JSON dump
>>> of the Google Code issues into JIRA's format, and INFRA imports that
>>> into the instance. The other is to write a script to insert all the
>>> issues via the JIRA API. I think both are tenable, but there's a few
>>> issues with both.
>>> To import the issues we need Infrastructure's assistance (AFAIK),
>>> because that's an administrative option on the JIRA instance.
>>> Converting the issues themselves is something we can do without
>>> intervention it seems. I believe we could also go forward with loading
>>> the issues via scripting on the API, but the issue with that is I
>>> don't know of any instance we can test the script against, so it'd be
>>> very hard to get perfect the first time. Therefore to me we either
>>> really need the Infrastructure team's assistance, or a potentially
>>> external JIRA instance to play with.
>>> Thoughts? Suggestions? I'd be happy to assist with whatever needs to
>>> be done to move this forward.
>>> -Ian
> --
> Any world that can produce the Taj Mahal, William Shakespeare,
> and Stripe toothpaste can't be all bad. (C.R. MacNamara, One Two Three)

View raw message