445928 - need a way to get components by their owner or qa contact using WebService API

Status: NEW

(Bugzilla :: WebService, enhancement, P2)

Description

[Noura Elhawary]

Hi,

We need a way to get a list of the components by their owner or qa contact, currently in bugzilla 3.2 editusers.cgi web interface there is a bottom section with "Product Responsibilites" that shows all components that a user is an owner of or a qa contact. We need to have similar functionality in the WebService API, so basically I think we can do that in one of the following ways:

1- extend WebService function User.get to return product responsibilites for each user along with the rest of the info it returns?

2- have a separate new function either in Component.pm or User.pm WebService modules to do that new functionality.

What do you think? thoughts?

Noura

Comment 1

[Max Kanat-Alexander]

(In reply to comment #0)
> 2- have a separate new function either in Component.pm or User.pm WebService
> modules to do that new functionality.

  Why not just have that as an argument to Component.get?

Comment 2

[Noura Elhawary]

(In reply to comment #1)
> (In reply to comment #0)
> > 2- have a separate new function either in Component.pm or User.pm WebService
> > modules to do that new functionality.
> 
>   Why not just have that as an argument to Component.get?
> 
sounds good to me, so we would have an argument 
$rpc->call('Component.get', {user => '[e-mail]'}); and then in the function we would call function $user->product_responsibilities; to get the list of the components/products that the user is a responsible for as an owner or as a qacontact.

that also brings up to my mind , enabling getting components by product so we would be able to get components by products, so in summary Component.get should enable us to get components by:

1- user
2- component name and product name
3- component id
4- product name

then with the return format shall we make the returned components grouped by product names as the following:

{ component_list => [ product1 => [ {comp1 details}, {comp2 details}],
                      product2 => [ {comp3 details}, {comp4 details}] 
                    ]
}  

Thanks,
Noura          

Comment 3

[Max Kanat-Alexander]

(In reply to comment #2)
> sounds good to me, so we would have an argument 
> $rpc->call('Component.get', {user => '[e-mail]'});

  Oh, I was thinking more like having assigned_to and qa_contact.

  We could do "user" too, I suppose. It should be an array, of course.

> that also brings up to my mind , enabling getting components by product so we
> would be able to get components by products, 

  Yeah. I'm pretty sure we have a separate bug for that.

Comment 4

[Frédéric Buclin]

We are going to branch for Bugzilla 4.4 next week and this bug is either too invasive to be accepted for 4.4 at this point or shows no recent activity. The target milestone is reset and will be set again *only* when a patch is attached and approved.

I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else.