On 13 September 2021, Red Hat’s Bugzilla team released updates to Bugzilla that included new functionality for pagination. There is also a change to the default number of results with the bug search API to support this feature. The default is now 20 but can be adjusted to 1000 by using the limit/offset parameters.
Pagination for Bugzilla Data Tables
Bugzilla now supports Pagination for data tables, improving performance by not loading all results at one time. As users navigate through pages, results will be lazy-loaded. Users can perform bulk actions on the list by selecting the rows from the list.
Changes to Bugzilla list API response
The default Bug search API(REST/XMLRPC/JSONRPC) result in 20 bugs by default and users can change this by specifying the limit. The value of limit can be up to 1000 bugs. If you need results that are more than 1000, you can use the offset parameter. You can get default 1000 bugs by sending 0 as a limit parameter.
Additionally, they have introduced “total_matches”, “limit”, and “offset” values in the response. These give the total number of bugs qualified for the query and the number of results in the response.
You can also set your account’s default limit in user preferences. The account default can be set as high as 200. You can still use the limit parameter to get up to 1000 bugs.
Since many unauthenticated calls come to Bugzilla, which just scans for results, they have decided to limit the number of results to be 20 bugs; Buglist API will not respect limits in this case. If you authenticate your query, you can set the limit as described above.
Note: Depending on the number of fields and data requested, your query can timeout.