I reiterate: the big issue I see is migrating users. We do not have access to user email addresses.
- How many users are there? - Will we manage user accounts in the new system? - What process do we have to allow users to claim accounts? - How do we coordinate this management with other projects, such as GeoTools? Humorous JIRA migration anecdote time: a once-well-known GeoServer developer had internal organisation (non-GeoServer) JIRA login "RobA"; when this JIRA instance was migrated to corporate JIRA where his corporate standard login was "atk093", corporate IT used a case-insensitive and context unaware search and replace on the exported XML to transform logins to the corporate standard. Unfortunately this affected all text. Every instances of the word "probably" was converted to "patk093bly", and a new piece of jargon was born. :-) Kind regards, Ben. On 03/03/15 10:31, Robert Coup wrote: > FWIW, notes on importing Issues into JIRA Cloud from another JIRA instance > are here: > https://confluence.atlassian.com/display/Cloud/Importing+Issues#ImportingIssues-ImportingissuesfromJIRAandotherthird-partyissuetrackers > > Looks like you just need a backup of the data + attachments exported from > the existing instance. > > Rob :) > -- Ben Caradoc-Davies <[email protected]> Software Engineer Transient Software <http://transient.nz> New Zealand ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
