Description of problem: Please, provide a XML-RPC call for cloning bugs. It's important for MPO [1] project automation and probably more than that. Inclusion of this functionality in python-bugzilla was discussed in [2] and denied. [1] http://wiki.brq.redhat.com/BaseOS/Man_pages_overrides [2] https://lists.fedorahosted.org/pipermail/python-bugzilla/2013-March/000053.html
Dear Martin, can you elaborate why you can not use Bug.get and Bug.create API calls? Thanks!!
I can, as you can see in the proposed patch for python-bugzilla in Comment #0. Aforementioned mailing list reference contains the rationale for this rfe.
Dear Martin, I've checked the mailing list. I have no doubt, that cloning bugs will be a very useful feature to you, as you have outlined in your proposal for your patch on the mailing list. I can't find the post which explains why you can not use Bug.get and Bug.create tho. Perhaps you can point me to the posting on the mailing list to get a better understanding. Thank you!
Hi Roman; Using Bug.get and Bug.create XML-RPC calls would be qualitatively the same as what I already did with respective python-bugzilla calls in my patch. I can do that, but it's not what I want. My goal is to move the bug cloning feature from my scripts directly to the bugzilla XML-RPC interface so that it will live along with already existing web UI feature keeping the design clean. Do you like my idea?
(In reply to comment #3) > Dear Martin, > > I've checked the mailing list. I have no doubt, that cloning bugs will be a > very useful feature to you, as you have outlined in your proposal for your > patch on the mailing list. > > I can't find the post which explains why you can not use Bug.get and > Bug.create tho. Perhaps you can point me to the posting on the mailing list > to get a better understanding. > > Thank you! The mailing list posting was here: https://lists.fedorahosted.org/pipermail/python-bugzilla/2013-March/000053.html The jist of my response is that it's just duplicating all the clone logic in an external script. If people start depending on that external script, the bugzilla clone starts doing something much different or adds some critical piece, the external script doesn't pick it up. Granted that's more of an argument for why it _shouldn't_ be implemented in python-bugzilla, I don't want to be responsible for that potential future breakage. But I figured it doesn't hurt to run it by our BZ guys since they've been pretty helpful in getting things upstream lately.
Dear Martin and Cole, from our current point of view, we will not be able to implement the request in the near future. Currently we need to focus on improving the Bugzilla performance. I can see were Martin is coming from, however it is best addressed upstream. That is, filing a bug at http://bugzilla.org. Why? Even if we would have currently the time and resources to implement the feature, it would be a RH only patch we would need to maintain. The best way to get this included in the Webservice is to convince the upstream maintainers. Good luck!
I'm closing this report. Please reopen or file a new bug report in case there is more to add to this issue. Thanks!