Skip to content

feat: list_tasks counts by board and status, assignee, status, label or due period, and on the boards the user manages EXO-94360 - #740

Merged
bmestrallet merged 2 commits into
feature/rtdfrom
feat/EXO-94360-group-by-counts
Nov 16, 2026
Merged

bmestrallet merged 2 commits into
feature/rtdfrom
feat/EXO-94360-group-by-counts

Conversation

@bmestrallet

Copy link
Copy Markdown
Contributor

Why. Asked « how many tasks per person », « by status for every project I manage » or « what is due this week », the Tasks assistant had one grouped count, board by board, and read pages or called a tool once per board, person or status for the rest. In evaluation runs those loops hit the per-turn call cap before the answer.

How.

  • list_tasks takes group_by:
    • project: as group_by_project, each listed board also split by_status (status id, name, count) in the board's column order;
    • assignee: the tasks with no assignee under « unassigned »;
    • status: the status name as the user reads it, a default status in the user's language. Statuses read the same, such as InProgress and RequestInProgress, make one group;
    • label: the labels of the task's own board, the ones its card shows, with « no label » counted on its own;
    • due_period: overdue, this week (today to Sunday), next week, later, none, in the user's time zone.
  • Every grouping returns groups (key, name, count, open_count), group_count, groups_not_listed past 100, group_by and a summary sentence. A grouped call with limit 1 says has_more false, as with group_by_project.
  • open_count is the group's open tasks the user can access, within project_id and managed_only, without the other filters. For overdue, it is the overdue tasks; count there includes completed tasks unless hide_completed_tasks.
  • managed_only narrows the listing and its counts to the boards whose managers hold one of the user's memberships, the reading of list_projects managed_only with no space; no personal task.
  • group_by_project stays; group_by_project true with another group_by is refused.
  • A new TaskHandler#countTasksByGroup runs one GROUP BY over the listing's own conditions, counting each task once per group. A new TaskQuery#setManagedBy and #setWithoutBoardLabel serve managed_only and « no label ». Each is tested on the engine.
  • The list_tasks description names the new parameters and fields. Its earlier definition joins ai-tool-definition-upgrades.json, pinned in the upgrades test.

Stacked on #739. Part of EXO-94360 (B0.5): the Tasks agent text naming each grouping follows in a Meeds-io/ai change once this lands.

Knowledge: pending — EXO-94360
Classification: N1: the label grouping decides which labels, other users' personal labels among them, a read-only MCP tool counts and names (scoped to the task's own board); also a new hand-written Criteria query on a list endpoint and a changed MCP tool definition (no require_approval change); no REST, schema or write path. Its approver must be an Architect who knows it is N1.

🤖 Generated with Claude Code

bmestrallet and others added 2 commits November 16, 2026 07:42
…or due period, and on the boards the user manages EXO-94360

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…tuses the user reads the same, and reads managed boards from their managers EXO-94360

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@bmestrallet
bmestrallet requested a review from ahamdi November 16, 2026 09:46
@bmestrallet

Copy link
Copy Markdown
Contributor Author

Self-review close-out — 6cdd000

Delivery checks before each round. Reviewer round 1, a second delivery-checks pass on its fixes, then a closing round with a fresh reviewer, clean but for one nit, fixed. The mutation run found two test gaps; both are fixed and confirmed.

# Round Sev Finding Status
1 delivery checks 🟡 The « no label » count was never run on the engine fixed: engine test
2 1 🟠 group_by label counted and named other users' personal labels and other boards' labels fixed: a task's own board's labels only, engine-tested
3 1 🟡 Status groups and by_status gave stored names while items show translated ones fixed: the name the user reads
4 1 🟡 managed_only bound an IN list of every managed board's id fixed: the managers' memberships, the list_projects managed_only rule
5 1 🟡 The definition was silent on a group's open_count and on overdue counting completed tasks fixed
6 1 🟢 Board-status order on a null rank was engine-dependent fixed
7 1 🟢 The definition did not say assignee keys are usernames fixed
8 1 🟢 « Not with group_by_project set to true » also refused the accepted project + true fixed: « for another grouping »
9 delivery checks 2 🟡 Label groups counted labels that a task's card does not show fixed: board labels only, as items show them
10 delivery checks 2 🟡 Two statuses read the same (InProgress, RequestInProgress) gave two same-named groups fixed: merged, counts summed
11 delivery checks 2 🟢 The definition said open_count ignores every other filter, yet it keeps project_id and managed_only fixed
12 closing 🟢 The TaskGrouping.LABEL Javadoc still described every label fixed
13 mutation run 🟡 A group's open_count read from the selected tasks and a dropped name order both survived fixed: tests pin both

Verified conform.

  • Each grouping is one GROUP BY over the listing's own conditions, with countDistinct on the task, so a task counts once per group. The open counts run once more, on the open tasks the user can access, within project_id and managed_only and none of the other filters.
  • A grouped call with limit 1 returns has_more false; groups_not_listed counts the groups past 100.
  • managed_only reads status.project.manager against the user's memberships, the ProjectQuery#setManager rule; the listing then holds no personal task.
  • The earlier list_tasks digest is in ai-tool-definition-upgrades.json (24 earlier definitions, pinned in the upgrades test); the new one is not.
  • Targeted: 198/0.
  • Mutation-verified: 30/30 killed.
  • Full suite -pl services -am verify -Prun-its -Pcoverage at 6cdd000: UT 505/0, IT 13/0; « All coverage checks have been met ».

Classification (computed on 739444dfa..6cdd000f6, this PR's two commits on top of #739): N1. The label grouping decides which labels a read-only MCP tool counts and names (other users' personal labels among them; scoped to the task's own board). There is also a new hand-written Criteria query on a list endpoint and a changed MCP tool definition, with no require_approval change. Its approver must be an Architect who knows it is N1.

@sonarqubecloud

Copy link
Copy Markdown

Base automatically changed from feat/EXO-94360-grouped-list-tasks-summary to feature/rtd November 16, 2026 10:24
@bmestrallet
bmestrallet merged commit 6cdd000 into feature/rtd Nov 16, 2026
9 checks passed
@bmestrallet
bmestrallet deleted the feat/EXO-94360-group-by-counts branch November 16, 2026 10:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant