www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-9954) Create ASTERIXDB Issues from Google Code import
Date Sun, 09 Aug 2015 10:10:45 GMT

    [ https://issues.apache.org/jira/browse/INFRA-9954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679078#comment-14679078

Gavin commented on INFRA-9954:

Ok now are getting somewhere.

I still had errors and failed imports for a few runs, but those errors I could fix on this
I needed to create lots of 'Statuses' like 'WontFix', 'Invalid' and a dozen others.
Those Statuses should really have been 'Resolutions' but at this stage I wasn't going to
argue the point if it gets us a successful import.

Situation now is we have a complete import success; 1061 issues imported.

We have them spread out amongst several different statuses.

However I am listed as the Reporter and Commentor for most of the issues - Not something I'm

too happy with.

What are the chances that you could alter the JSON file and replace all values of Reporter
and Commentor with a 
user called 'asterixdb-importer' or similar.??

If so , I'll blow away all the issues and do another clean import from scratch.

Take a browse around https://issues.apache.org/jira/browse/ASTERIXDB for the current situation.

> Create ASTERIXDB Issues from Google Code import
> -----------------------------------------------
>                 Key: INFRA-9954
>                 URL: https://issues.apache.org/jira/browse/INFRA-9954
>             Project: Infrastructure
>          Issue Type: New JIRA Project
>          Components: JIRA
>            Reporter: Ian Maxon
>            Assignee: Gavin
>         Attachments: Asterixdb-1421.log, Screen Shot 2015-08-05 at 10.41.47 am.png, Screen
Shot 2015-08-05 at 11.14.55 am.png, adb_jira_issues.json, asterixdb_import_attempt.log, asterixdb_import_error_from_db-1.0.log,

This message was sent by Atlassian JIRA

View raw message