128613 - Need to be able to specify product/component when moving a bug

Status: NEW

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

Description

[Dave Miller [:justdave]]

An item for consideration here: in most of the cases when moving bugs between
Bugzilla's Bugzilla installation and Mozilla's installation the source product
is going to be different from the destination product, and may not be the same
one in all cases (i.e. Browser or mozilla.org).  Need to allow some way to
specify the product/component on the desination side from the source side when
moving the bug.

Comment 1

[Bradley Baetz (:bbaetz)]

Thats going to be hard, since you don't ahave a list of products on the other
site. I guess we could have a config.cgi page which could spit out xml, but that
requries that the one instance can talk to the other.

Comment 2

[Dave Miller [:justdave]]

Which is already a given (the sites having to be able to talk to each other).
See bug 127875.

Comment 3

[Myk Melez [:myk] [@mykmelez]]

>I guess we could have a config.cgi page which could spit out xml

This is bug 72837.

Comment 4

[Dave Miller [:justdave]]

I thought bug 72837 was going to spit out Javascript, rather than XML...  or can
it maybe do both? :)

Comment 5

[Myk Melez [:myk] [@mykmelez]]

>I thought bug 72837 was going to spit out Javascript, rather than XML...  or can
>it maybe do both? :)

Bug 72837 uses formats just like the buglist.cgi templatization patch in bug
103778, so it can generate output in any format for which someone develops a
template.  Formats supported by the (admittedly bitrotted) patch on that bug
currently include JavaScript and RDF (an XML dialect).

Comment 6

[Dave Miller [:justdave]]

Reassigning bugs that I'm not actively working on to the default component owner
in order to try to make some sanity out of my personal buglist.  This doesn't
mean the bug isn't being dealt with, just that I'm not the one doing it.  If you
are dealing with this bug, please assign it to yourself.

Comment 7

[Max Kanat-Alexander]

Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?". Then, either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.

This particular bug has not been touched in over eight months, and thus is being retargeted to "---" instead of "Bugzilla 4.0". If you believe this is a mistake, feel free to retarget it to Bugzilla 4.0.

Comment 8

[Beth Johnson]

Attachment: same problem

Thanks from theobroseqas1981.