We are using MantisBT 2.26.2 with REST API enabled ($g_enable_rest_api = ON; and $g_webservice_rest_enabled = ON;).
The following API call works as expected and returns issues for a project:
GET http://192.168.0.170:8082/bugtracker/ap ... ject_id=87
However, when we add additional query parameters like status_id, page, or per_page, they are ignored. Example:
GET http://192.168.0.170:8082/bugtracker/ap ... er_page=10
This still returns all issues under the project, without filtering by status or applying pagination.
We also tested the /api/rest/config endpoint, but it only returns:
{
"configs": []
}
Questions:
1. Is this the expected behavior in MantisBT 2.26.2?
2. Are status_id, page, and per_page supported query parameters in the REST API, or do we need to use a saved filter_id for filtering and pagination?
3. If filters are only supported via filter_id, is there any plan to extend query parameter support in future releases?
Environment:
• MantisBT Version: 2.26.2
• Server: WAMP (Windows, Apache, MySQL, PHP)
• REST API enabled in config_inc.php
REST API does not apply filters (status_id, page, per_page) in MantisBT 2.26.2
Moderators: Developer, Contributor