Add triage owner in /rest/bug

RESOLVED FIXED

Status

()

--
enhancement
RESOLVED FIXED
4 months ago
4 months ago

People

(Reporter: calixte, Assigned: dylan)

Tracking

Production

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 2 obsolete attachments)

(Reporter)

Description

4 months ago
We should have an entry for triage_owner instead of querying /rest/product to get it.
Assignee: extensions → nobody
Component: Extensions → API
Product: Bugzilla → bugzilla.mozilla.org
QA Contact: default-qa
Version: unspecified → Production
Assignee: nobody → kohei.yoshino
Severity: normal → enhancement
Status: NEW → ASSIGNED
See Also: → bug 1489120
(Reporter)

Comment 2

4 months ago
If we could have triage_owner_detail as we've for creator then it'd be nice (to avoid to make a query on user).
(Reporter)

Comment 3

4 months ago
:kohei, you guessed my needs, thx (I didn't read your patch before doing my comment).
Yes, triage_owner_detail is there :)
Merged to master.
Status: ASSIGNED → RESOLVED
Last Resolved: 4 months ago
Resolution: --- → FIXED
(Assignee)

Comment 6

4 months ago
This cannot work like this.

We can return a new top level thing, triage_owners, that is indexed by product and component but adding this to each bug result will use fantastically more memory
Reopening. This will need to be reimplemented differently in order to not increase memory usage for the API.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Attachment #9024035 - Attachment description: GitHub Pull Request → GitHub Pull Request to revert the initial PR
Attachment #9024035 - Attachment is obsolete: true
Merged to master. again.
Status: REOPENED → RESOLVED
Last Resolved: 4 months ago4 months ago
Resolution: --- → FIXED
(Reporter)

Comment 11

4 months ago
thanks guys, it's ok for me like this.
(Assignee)

Comment 12

4 months ago
So memory usage has exploded because people ask for _custom all the time
Assignee: kohei.yoshino → dylan
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
But _custom won’t return triage owners. Just _extra or triage_owner.
Also user objects are cached and there aren’t so many triage owners, right?
Dylan mentioned using an intermediate layer like GraphQL to cache this information. That layer could do the join, or consuming applications could just fetch the list of Triage Owners and do the join on their own.
(Assignee)

Comment 16

4 months ago
plenty of API customers use _extra and _custom, but for the moment this can ride.

Something like GraphQL would help, because it would encourage people to use paging. Right now some customers expect 4000-5000 or more bugs per request.
Status: REOPENED → RESOLVED
Last Resolved: 4 months ago4 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.