Repository navigation
fix: list_tasks names the boards the user manages beside the boards holding tasks, and counts each board's overdue tasks EXO-94360 - #743
Conversation
…olding tasks, and counts each board's overdue tasks EXO-94360 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…t, whose counts reach that board alone EXO-94360 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…her filters, and names the managed boards with no open task beside open tasks only EXO-94360 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…erdue count ignores EXO-94360 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…he user manages holds open tasks EXO-94360 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…94360 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Self-review close-out — 4ac6fbaDelivery checks, two reviewer rounds, then a closing round with a fresh reviewer. Every finding was fixed and verified in the source. The mutation run found one test gap, which is now fixed and confirmed.
Verified conform.
Classification (computed on |
… and the totals before the lists, and totals the managed boards' idle boards and overdue tasks EXO-94360 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…a count no other filter narrows, and writes each status before its count EXO-94360 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…t in one call, the grouped answer's fields in their parameters EXO-94360 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Self-review close-out — follow-up 4ac6fba..6f78a56The follow-up has three commits on top of the reviewed 4ac6fba:
Why. A later evaluation found two problems, which these commits fix:
Verified conform.
Classification (computed on |
|



Why. In evaluation runs, the Tasks assistant was asked for « the status of every project I manage ». It answered « you manage 86 projects » when the user manages 105. The grouped
list_taskssummary read « 1630 open tasks in 86 of 86 boards the user manages », but the 86 were the managed boards that hold open tasks: a board with no task never appears in a count made from its tasks. The same answer needed a secondoverdue_onlycall for the overdue figures. Its board rows have the same shape as the first call's, and the assistant read one call's status split as the other's. A later run showed two more causes:by_statusentries, each with its owncount, came before the board'scount, and the assistant read a status's count as the board's;list_tasksdescription, the assistant called the tool less often.How.
managed_onlyand noproject_id, a groupedlist_tasksanswer givesmanaged_project_count: every board the user manages, boards with no task included. It uses the query and the distinct countlist_projectsmanaged_onlygives with no space. With aproject_id, the counts cover that one board, so no total is given.overdue_count, using theoverdue_onlyrule: open tasks due before today in the user's time zone, withinproject_idandmanaged_only, without the call's other filters. One grouped call now gives each board's selected, open and overdue tasks and their split by status.managed_only, noproject_id), the answer also gives three totals:idle_project_count: the managed boards holding no open task;overdue_count: the overdue tasks of every managed board, from the query each board'soverdue_countreads, the boards left out ofprojectsincluded;overdue_project_count: the boards that hold them.The summary then ends with « ; 264 overdue in 30 boards », unless another filter narrows the count or the call selects overdue tasks only.
project_id, project_name, count, open_count, overdue_count, by_status, a status readsstatus_id, status, count, and a grouped answer gives its totals beforeprojectsandtasks.@JsonPropertyOrderon the three models makes this hold whatever their constructors.list_tasksdescription is shorter than before this PR, 1,432 characters against 3,006. It says what the tool does and to count by board, assignee, status, label or due period in one grouped call. The grouped answer's fields are described in thegroup_by_project,group_byandmanaged_onlyparameters. The earlier definition joinsai-tool-definition-upgrades.jsonand is pinned in the upgrades test.Part of EXO-94360 (B0.5): the Tasks agent text that reads these fields follows in a Meeds-io/ai change.
Knowledge: pending — EXO-94360
Classification: N1: it changes which boards a read-only MCP tool counts and names as the user's managed boards (reusing the
list_projectsmanaged selection), adds a count to an access-scoped task query on a list endpoint, and changes an MCP tool definition (norequire_approvalchange); no REST, schema or write path. Its approver must be an Architect who knows it is N1.🤖 Generated with Claude Code