www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Turner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-1963) Merge Struts JIRA into main JIRA
Date Mon, 04 Jan 2010 14:37:54 GMT

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

Jeff Turner commented on INFRA-1963:

I'd like to have a go at this in the next week. Doing it requires:
- minimize clashing logins by renaming users in the Struts JIRA to equivalent (by email address)
users in the main JIRA before import, to prevent duplication.
- email renamed users letting them know their Struts username has been renamed.
- creating things (custom fields, groups) in the main JIRA that the Project Importer won't
work without. 
- doing Project Imports in JIRA.  The Project Importer locks everyone out of JIRA for the
duration of the import, and as that is likely to take about 2 hours (just importing Struts
1 and 2 takes JIRA 30 and 20 minutes respectively), we should rather put a read-only copy
of the main and Struts JIRAs up.
- reestablishing lost things like notification schemes, permission schemes, custom screens,
issues-from-email, Subversion links.
- import (via SQL hackery) saved searches from Struts JIRA.
- import (more SQL hackery) copyright attachment info.

I noticed that XWork is partially imported (the attachments are missing) into the Struts JIRA,
but hidden from non-admins. It will probably be easier to import it directly from jira.opensymphony.com.

> Merge Struts JIRA into main JIRA
> --------------------------------
>                 Key: INFRA-1963
>                 URL: https://issues.apache.org/jira/browse/INFRA-1963
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: JIRA
>            Reporter: Henri Yandell
>            Assignee: Jeff Turner

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message