Compare: a) https://api-dev.bugzilla.mozilla.org/latest/bug?whiteboard=orange&include_fields=id&summary=browser_frameworker.js b) https://api-dev.bugzilla.mozilla.org/latest/bug?whiteboard=orange&summary=browser_frameworker.js c) https://api-dev.bugzilla.mozilla.org/latest/bug?whiteboard=orange&include_fields=id,resolution&summary=browser_frameworker.js Expected: a+b+c have the same sort order. Actual: a+b have the order... id: 766826 id: 797874 id: 776554 whereas c has: id: 797874 id: 776554 id: 766826 In bug 799637 I went to do what I had hoped would be a simple addition of "&include_fields=id,summary,status,resolution" (in order that TBPL doesn't cause unnecessary load, given that the server-side does in the order of ~5000 bzAPI requests a day, and until recently we'd not been specifying include_fields), but this change in sort order means that resolved bugs no longer appear below open in the TBPL bug suggestion lists (and yeah we should really be sorted the json results, but this still seems like a bug).
Summary: Adding resolution to include_fields changes returned results sort order → Adding resolution to include_fields changes sort order
This bug was fixed by the checkin for bug 800835. Gerv
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.