Closed
Bug 1505793
Opened 6 years ago
Closed 6 years ago
Add triage owner in /rest/bug
Categories
(bugzilla.mozilla.org :: API, enhancement)
Tracking
()
RESOLVED
FIXED
People
(Reporter: calixte, Assigned: dylan)
References
Details
Attachments
(1 file, 2 obsolete files)
We should have an entry for triage_owner instead of querying /rest/product to get it.
Updated•6 years ago
|
Assignee: extensions → nobody
Component: Extensions → API
Product: Bugzilla → bugzilla.mozilla.org
QA Contact: default-qa
Version: unspecified → Production
Updated•6 years ago
|
Assignee: nobody → kohei.yoshino
Severity: normal → enhancement
Status: NEW → ASSIGNED
See Also: → 1489120
Comment 1•6 years ago
|
||
Reporter | ||
Comment 2•6 years 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•6 years ago
|
||
:kohei, you guessed my needs, thx (I didn't read your patch before doing my comment).
Comment 4•6 years ago
|
||
Yes, triage_owner_detail is there :)
Comment 5•6 years ago
|
||
Merged to master.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•6 years 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
Comment 7•6 years ago
|
||
Reopening. This will need to be reimplemented differently in order to not increase memory usage for the API.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 8•6 years ago
|
||
Comment 9•6 years ago
|
||
This makes `triage_owner` an extra field so you’ll have to use the `include_fields` param like this: https://bugzilla.mozilla.org/rest/bug/1505793?include_fields=_default,_extra https://bugzilla.mozilla.org/rest/bug/1505793?include_fields=_default,triage_owner https://bugzilla.mozilla.org/rest/bug/1505793?include_fields=id,summary,triage_owner (or whatever you want)
Attachment #9023666 -
Attachment is obsolete: true
Updated•6 years ago
|
Attachment #9024035 -
Attachment description: GitHub Pull Request → GitHub Pull Request to revert the initial PR
Attachment #9024035 -
Attachment is obsolete: true
Comment 10•6 years ago
|
||
Merged to master. again.
Status: REOPENED → RESOLVED
Closed: 6 years ago → 6 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 11•6 years ago
|
||
thanks guys, it's ok for me like this.
Assignee | ||
Comment 12•6 years ago
|
||
So memory usage has exploded because people ask for _custom all the time
Assignee: kohei.yoshino → dylan
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 13•6 years ago
|
||
But _custom won’t return triage owners. Just _extra or triage_owner.
Comment 14•6 years ago
|
||
Also user objects are cached and there aren’t so many triage owners, right?
Comment 15•6 years ago
|
||
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•6 years 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
Closed: 6 years ago → 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•