List issues
list_issuesSearch, filter, and count Taiga project issues by type, status, open/closed, severity, priority, assignee, tag, creation/closure date, or text; results show newest first.
Instructions
List, search or count issues (bugs, questions, enhancement requests) of a Taiga project, most recently created first: reference number, type, title, status, severity, priority and assignee. Filter by type, status, open or closed, severity, priority, assignee, tag, the days they were created or closed in, or words in the text (search: "login timeout"). The heading gives the count of all matches. Planned work is user stories: use list_user_stories. For the description and comments of one issue use get_item.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"project": "<project>"
},
"name": "list_issues"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | Only items that carry this tag, e.g. "backend". get_project lists the tags of a project. | |
| page | No | Which part of a long list, counted from 1. When an answer says more items exist, call again with the next page and the same `limit` and filters. | |
| type | No | Exact issue type name, e.g. "Bug". A wrong name is answered with the valid ones. | |
| limit | No | Most items to return in one answer (default 30, at most 100). The answer says how many more exist. | |
| closed | No | false: only items still open ("not done yet", "remaining"). true: only closed ones. Leave out for both. | |
| search | No | Words to look for in titles, descriptions and tags, e.g. "invoice export". An item must contain every word; a word also matches the beginning of a longer one. Use it when the user describes an item instead of giving its number. | |
| status | No | Exact status name, e.g. "Needs Info". Each project defines its own; a wrong name is answered with the valid ones. For "open" or "done" in general use `closed` instead. | |
| project | Yes | Project slug as given by list_projects, e.g. "acme-billing". Not the display name. | |
| priority | No | Exact priority name, e.g. "High". A wrong name is answered with the valid ones. | |
| severity | No | Exact severity name, e.g. "Critical". A wrong name is answered with the valid ones. | |
| created_to | No | Only items created on or before this day, as YYYY-MM-DD (UTC). | |
| assigned_to | No | Only items assigned to this person: full name or username as in Taiga; part of the name is enough when it fits one member only, and accents may be left out. "unassigned" for items assigned to nobody. A name that does not fit is answered with the members. For the signed-in user use `assigned_to_me`. | |
| finished_to | No | Only items closed on or before this day, as YYYY-MM-DD (UTC). Items still open are left out. | |
| created_from | No | Only items created on or after this day, as YYYY-MM-DD (UTC). | |
| finished_from | No | Only items closed on or after this day, as YYYY-MM-DD (UTC). Items still open are left out. | |
| assigned_to_me | No | true: only items assigned to the signed-in user ("my stories", "assigned to me"). |