List issues
mantis_list_issuesRead-onlyIdempotent
List and filter MantisBT issues with lightweight summaries, supporting server-side project and filter selection, plus client-side filtering by status, assignee, reporter, and date ranges.
Instructions
List issues (newest id first). Returns a LIGHTWEIGHT summary per issue by default (id, summary, status, handler, reporter, priority, dates…) — call mantis_get_issue for notes/attachments/history. Filter server-side by project_id / stored filter_id. The status, assigned_to, reporter_id and date filters are applied client-side (the REST API lacks them); when active, multiple pages are scanned (up to 500 issues). Use status="open" for all not-yet-resolved issues. Omit project_id to span all projects.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 1-based page number (default 1). | |
| select | No | Comma-separated fields to include. Defaults to a lightweight summary set. Fields needed by the active filters are always fetched even if omitted here. | |
| status | No | Status name (localized or canonical) or "open" for all not-yet-resolved issues (client-side). | |
| filter_id | No | Stored Mantis filter id (see mantis_list_filters). | |
| page_size | No | Issues per page (default 50). | |
| project_id | No | ||
| assigned_to | No | Handler/assignee user id (client-side filter). | |
| reporter_id | No | Reporter user id (client-side filter). | |
| created_after | No | ISO-8601 timestamp — only issues created strictly after this. | |
| updated_after | No | ISO-8601 timestamp — only issues updated strictly after this. Example: "2026-03-25T00:00:00Z" | |
| created_before | No | ISO-8601 timestamp — only issues created strictly before this. | |
| updated_before | No | ISO-8601 timestamp — only issues updated strictly before this. |