335437 - Create a UI for importxml.pl

Status: RESOLVED WONTFIX

(Bugzilla :: Bug Import/Export & Moving, enhancement)

Description

[Frédéric Buclin]

Having a UI for importxml.pl would be really helpful. Actually, importxml.pl offers no alternative when it meets a product, a component, a flag or a user which doesn't exist in the new DB and drops them. Having a UI would permit us to decide what to do in this case, such as:

- Product 'foo' doesn't exist. Create it?
- Flag 'bar' doesn't exist for that product. Create it?
etc...

Comment 1

[Guzmán Brasó]

I like the idea but how could be this implemented?.

The only way I see would be to setup a queue of imported bugs that failed and let the administrator check that queue and change appropiate fields to make it fit into destination installation or choose to discard and send an e-mail.

But, there is always a but... current way of work will require at the long term lot of less work than this suggested CR.

For example, if a bug go to a installation like you said with different product, component, flag or user, bug get rejected and you get an e-mail telling you why the bug was rejected.
Then you as administrator go to the installation and fix the issue: you add the missing flag, you correct/add the missing user, you correct/add the missing component. 
From this point you will never have to correct/add the same mistake.

If we implement a queue for bugs that failed to import, besides spending some minutes setting up whatever you need to get the bug approved in the new installation, you will have to lost the same minutes any time another bug with the same component/user/flag/product is moved.

Tell me what you think... 

Comment 2

[Guy Pyrzak]

Shouldn't this be implemented as part of the web services architecture?

Comment 3

[Frédéric Buclin]

OK, I decided that this was definitely part of a separate project, and doesn't match Bugzilla goals. The way to go will be WebServices.