List epics
list_epicsList, search, or count Taiga project epics in board order with status, assignee, and story completion progress. Filter by status, assignee, tag, creation date, or text to spot work that is behind.
Instructions
List, search or count the epics of a Taiga project in board order: reference number, title, status, assignee, and how many of the user stories under each epic are done. Filter by status, open or closed, assignee, tag, the days they were created in, or words in the text. Use it for an overview of large pieces of work, to see which epics are behind (closed: false, then compare progress), or for "how many epics are mine" (assigned_to_me: true; the heading gives the count of all matches). For the stories under one epic call list_user_stories with epic. Dates kept in custom fields, the description and comments of one epic come from 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_epics"
}
}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. | |
| 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. "In progress". 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. | |
| 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`. | |
| created_from | No | Only items created on or after this day, as YYYY-MM-DD (UTC). | |
| assigned_to_me | No | true: only items assigned to the signed-in user ("my stories", "assigned to me"). |