List user stories
list_user_storiesList, search, or count Taiga project user stories by sprint, status, assignee, tag, epic, or dates to answer questions like what remains in the current sprint or backlog.
Instructions
List, search or count user stories of a Taiga project in board order: reference number, title, status, assignee, points and sprint. Filter by sprint, epic, status, open or closed, assignee, tag, the days they were created or finished in, or words in the text. Use it for questions such as "what is left in the current sprint" (sprint: "current", closed: false), "what is in the backlog", "what is Linh working on" (assigned_to: "Linh"), "how many stories did I finish in October" (assigned_to_me: true, finished_from, finished_to) or "the story about PDF export" (search: "pdf export"). The heading gives the count of all matches, so for "how many" a small limit is enough. Bugs and requests are issues: use list_issues. The small pieces of work inside a story are tasks: use list_tasks. For the description and comments of one story 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_user_stories"
}
}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. | |
| epic | No | Reference number of an epic from list_epics, without the #: only the stories under it. | |
| 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. | |
| sprint | No | A sprint name from list_sprints, or "current" for the sprint running today, or "backlog" for stories in no sprint. Leave out for stories of every sprint and the backlog. | |
| 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`. | |
| 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"). |