Triage Linear or Jira backlogs and run bug sweeps via the Composio CLI. Bulk-fetch issues, dedupe, relabel, reassign, and post summaries — all from the shell without clicking through the UI.

Issue Triage (Linear / Jira) Drive triage sessions and bug sweeps across Linear or Jira with the [Composio CLI](https://docs.composio.dev/docs/cli). Pull the backlog, cluster duplicates, apply labels, and hand a clean list back to the team. When to Use Weekly triage: "what's unassigned, stale, or missing a priority?" Bug sweep after a release: "cluster all P1/P2 bugs, dedupe, assign owners." Cross tool sync: Sentry → Linear, PagerDuty → Jira. Prereqs Discover Tools Common slugs (verify with get schema ): Linear LINEAR LIST ISSUES LINEAR CREATE ISSUE LINEAR UPDATE ISSUE LINEAR CREATE COMMENT Jira JIRA SEARCH FOR ISSUES USING JQL JIRA CREATE ISSUE JIRA EDIT ISSUE JIRA ADD COMMENT JIRA ASSIGN ISSUE Triage Workflow 1. Pull the backlog slice: 2. Cluster by title similarity and labels. The agent groups likely duplicates locally. 3. Apply updates in one pass (label, priority, assignee): 4. Link duplicates with comments referencing the canonical issue. 5. Post a digest of what changed to Slack so the team sees the sweep results. Bug Sweep (Post Release) Workflow File scripts/triage linear.ts , run with composio run file scripts/triage linear.ts : Cross Tool: Sentry → Linear Troubleshooting Unknown field names → composio execute <SLUG get schema shows the exact filter shape (Linear uses nested objects; Jira uses JQL strings). 403 on Linear → re run composio link linear with the right workspace. Jira custom fields missing → request them explicitly in the fields array. Bulk edits rate limited → insert a 250ms sleep in the composio run loop; don't use parallel . Full CLI reference: [docs.composio.dev/docs/cli](https://docs.composio.dev/docs/cli)

issue-triage