Triage bot: complete the read-tool set for workspace/planning questions (status, counts, releases)

Round out the agent's tools so it can answer the whole "state of the workspace / what's planned" class of question with real data (follow-on to PAR-227 ANSWER + PAR-229 list_tasks).

Added to the agentic loop (TriageService.runReadTool):

list_tasks status filter + count — now resolves a status name (e.g. "In Progress", "Pending Release") tenant-wide and returns a total count + rows, so "what's in In Progress", "how many open bugs" are answerable precisely (not capped/guessed).
list_releases — releases (workspace-wide or per project): title, open/shipped, issue count.
get_release — the issues in a project's current (open, else latest) release → "what's in / planned for the next release".

Port additions (TaskSystem + PostgresTaskSystem):

findStateId(String) — tenant-wide status resolution (statuses are tenant-scoped since V18; the old overload needed a groupId).
countTasks(TaskQuery) — same predicates as listTasks, shared WHERE builder.
TriageService now injects ObjectProvider<ReleaseService> (optional/null-safe).

Prompt: documents the full tool menu — search_tasks (keyword), get_task, list_tasks (project/assignee/label/status/priority/open + count), list_releases, get_release — and which question maps to which.

Tests: new PostgresTaskSystemTest.countTasksAndTenantWideStatusResolution; full backend suite green.

Activity

tesks created the issue Jun 18
ParadauxIO linked a commit: Commit 18170dd — Triage: complete the read-tool set for workspace questions (PAR-230) Jun 18

Workspace permission required to comment

Comments and reactions require workspace permission. Ask a workspace owner or admin for access. You can sign in to vote.