Launchpad itself

Is there support for the "affects" relation in XML bug history import?

Asked by Ralph Lange

Here's the situation:

I would like to import my project's bug history, and I'm preparing the exporter that creates the XML data according to your spec.
My LP project has three series, which were represented in the old bug tracker as three projects. How can I - in the XML - express the series that a bug affects?

Thanks for you help,
Ralph Lange

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
Graham Binns Edit question
Solved by:
Ralph Lange
Solved:
Last query:
Last reply:
Revision history for this message
Ralph Lange (ralph-lange) said : 		#1

This boils down to:
In the XML input format, how do I create bug tasks, and define their set of separate properties (status, project/series, assignee, importance, milestone)?
The XML (as described on the help pages) seems to only support a "flat" bug structure, without bug tasks, and thus using only one set of bug task properties.

If the XML import only supports a flat structure - would you consider it a possibility to generate the emails needed to create the bug task structures and then just bulk send them after the import has been done?

Thanks again,
Ralph Lange

Revision history for this message
Graham Binns (gmb) said : 		#2

Hi Ralph,

I don't know the answer for your question right away, but I will find out for you and get back to you by the end of this week.

Cheers,

Graham

Revision history for this message
Graham Binns (gmb) said : 		#3

Argh; I meant to hit "comment only."

Revision history for this message
Graham Binns (gmb) said : 		#4

Hi Raplh, sorry for not getting back to you sooner.

So, having looked at our schema and investigated a bit, it turns out that the schema only supports, as you suggested, a "flat" structure, i.e. each bug will only affect the project for which we're doing the import. This is intentional, I think, but it's worth investigating further whether this should be something we support. I'll file a bug about it.

I think the best solution at this time would be for you to use the Launchpad API (https://help.launchpad.net/API) to add the necessary bug tasks to the bugs once the bugs have been imported, since that's less prone to failure than using the email interface.

Revision history for this message
Graham Binns (gmb) said : 		#5

Hi Ralph,

Given what I've said above do you want to go ahead with the bug import?

Revision history for this message
Graham Binns (gmb) said : 		#6

Marked as needs info for admin purposes.

Revision history for this message
Ralph Lange (ralph-lange) said : 		#7

With the help of Deryck Hodge, the bug import was done on 2010-03-18 (see Question #98017).

Thanks again.