Comment 2 for bug 715754

The process that I, and other members of the former Bugs team who have
requested bug imports, follow is documented here:

  https://dev.launchpad.net/PolicyAndProcess/BugImportHowto

@LOSAs: It is linked to from the internal wiki:
  https://wiki.canonical.com/InformationInfrastructure/OSA/LPHowTo/ImportProjectBugs

It should be possible to move most of the first 4 steps into Launchpad
and end up with something like:

1. Validate bug data against the schema.

2. Massage the bug data (see utilities/massage-bug-import-xml in the
   Launchpad source).

   We could do some additional checks here, for example to see if bug
   nicknames are already in use.

3. Allow visual inspection of the bug data, and summarize what actions
   Launchpad will take with it, for example:

     Launchpad will import 119 bugs, create 23 new users, ...
     Of the 119 bugs, 8 are Critical, ...

4. Import the data into an existing project.

   An obvious place for the +import page would be something like
   https://bugs.launchpad.net/<project>/+import, so this step would
   not create the project for the user (as step 4.2 in BugImportHowto
   suggests).