Fedora Account System
Red Hat Associate
Red Hat Customer
write xmlrpc function editComponent that is to be contributed to the upstream. Please refer to the following url for details on Bugzilla::RPC 2.18 functions mapped to upstream Bugzilla::WebService and for 2.18 xmlrpc functions sorted by percentage of calls: https://engineering.redhat.com/trac/bugzilla-3.0-rh/wiki/XmlrpcCrossComparison#a2.18xmlrpcfunctionssortedbypercentageofcalls
Created attachment 291826 [details] new WebService Module Component.pm with xmlrpc function edit() attached is the new WebService module Component.pm I added to it xmlrpc function edit() which should replace our function editComponent(). One thing we need to discuss is that ,, in our current rh_bugzilla_2_18 we have in the xmlrpc function editComponent() code to re-assign bugs of the component, I am not really sure if we have to do that for the new function attached here which is edit() ?? In my opinion it is not necessary, and I think this functionality is rarely used. Noura
LOC Estimation: Inputs: hasref with component&product names and fields that will be edited = 1 Outputs: authentication errors , input validation errors, logging messages, hashref with changes details = 4 Inquiries: components data , user data, product data = 3 Logical files: Zero External files = Zero FP total count(simple weighting factor)= (3*1)+(4*4)+(3*3)+(7*0)+(5*0)= 25 FP = 25 * 1.11 = 28 LOC = 28 * 60 = 1680 For Unit testing: 100 LOC for one xmlrpc testcase total LOC = 1680+100 = 1780 LOC
changed the code for WebService Function Bugzilla::WebService::Component::update() submitted code upstream for review.
updated code to throw and error when updating name of multiple components of the same product + added POD
This feature is included now in Milestone 2. Any bugs found with this feature should be file as a new report and set to block the 3.2 final release tracker.