web interface for bug imports

Bug #715754 reported by Tom Haddon
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

This is a feature request for an interface in LP to allow a restricted set of users to be able to do their own bug imports without needing intervention from LOSAs. This would mean a way of uploading the .xml file, and specifying which project to associate them with, and then returning the result. This would need to be able to be done on [qa]staging as much as on production, when we're ready to do that, although it'd be a process question as to who would actually do this on production.

This would reduce the operational overhead of these requests, as we don't know enough about the data to validate it before running the bug import anyway, so we're not really adding any value there.

Revision history for this message
Tom Haddon (mthaddon) wrote :

Oh, and obviously if this could be done via the API that would probably be fine too - it doesn't necessarily need to be via the web interface.

tags: added: canonical-losa-lp
Revision history for this message
Gavin Panella (allenap) wrote :

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).

Curtis Hovey (sinzui)
tags: added: bugs chr
Changed in launchpad:
status: New → Triaged
tags: added: feature
Changed in launchpad:
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.