Description of problem: There should be a scriptable way to add to a bug the association with an external bug identifier, as can be done from the web interface. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Is this something that will come with 3.0? I don't even remember wanting this in particular (I've never used XMLRPC). I'm sure it was what dkl told me to file after discussing ideas about automatic bug escalation between RH and sourceware bugzilla.
Sorry for the long delay in responding this report :( Yes, this functionality should come with the 3.0 upgrade since the backend code will be improved enough to allow changing of all bug attributes through a single XMLRPC call. Currently we have hacked ours to have different methods to change individual attributes and unfortunately external bug references is not one of them currently. Let me know if you need this sooner than the 3.0 timeframe and maybe we can add the support in. Dave
I don't need an XMLRPC feature myself ever, certainly not by any particular deadline. My interest is in having you implement cool features for cooperation between this bugzilla and upstream bugzillas, whenever and however that can happen.
Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code. Updating bug version to 3.2.
Red Hat Bugzilla is now using version 3.4 of the Bugzilla codebase and therefore this feature will need to be implemented against the new release. Updating bug version to 3.2.
Red Hat has now upgraded to Bugzilla 3.6 and this bug will now be reassigned to that version. It would be helpful to the Bugzilla Development Team if this bug is verified to still be an issue with the latest version. If it is no longer an issue, then feel free to close, otherwise please comment that it is still a problem and we will try to address the issue as soon as we can. Thanks Bugzilla Development Team
*** This bug has been marked as a duplicate of bug 725627 ***