Add all the shown tickets to the AI queue, from the Tickets page heading - #1679
Merged
Conversation
A button beside the /tickets heading starts an unattended agent working exactly the tickets the current filters show, told to start nothing else. A shown set spanning several projects fans out one agent per project (an agent works inside one repo), and the button's label counts the tickets and the agents one click costs. A single shown ticket degrades to the row start's own one-ticket ask, ticket named on the agent (#1117). Page-level start failures now render under the heading, so grouped mode shows them too. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019vS2EK2vVFJc3oDCtrgShR
The heading button now spins up one agent per shown ticket instead of one batch agent per project: each unclaimed shown ticket is queued the way the detail page's Queue action queues it (#1164) — reusing an open entry that already links to it rather than writing a duplicate — and gets its own unattended agent started on that one entry, the queue card's per-entry start (#855), ticket named on the agent (#1117). Claimed tickets are left to the agents holding them, and the label counts only the agents one click costs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019vS2EK2vVFJc3oDCtrgShR
brillout
changed the title
"Add all X tickets shown below to the AI queue": every unclaimed shown ticket joins the AI queue exactly as the detail page's Queue action queues one (#1164), in the shown order, skipping tickets an open entry already links to. No agent starts — the queue is what the routine drain fans out over (#1204) and what the queue card's play buttons work one entry at a time (#855). After a click the button reads "Queued" and rests until the shown set changes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019vS2EK2vVFJc3oDCtrgShR
brillout
changed the title
"in the shown order, each in its priority section" read as two orders fighting; the tooltip now says how the queue is actually worked: highest priority first and, within a priority, in the order shown. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019vS2EK2vVFJc3oDCtrgShR
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the button beside the
/ticketspage heading: "Add all X tickets shown below to the AI queue".What it does
Queuebutton doesn't seem to work? #1164) — title as the entry, linked back to the ticket, its priority picking the section — walked in the shown order, so entries within a priority section keep the order the reader saw. Each ticket lands on its own project's queue, so cross-project views need no special case.Implementation
sendQueueTicket(the detail page's Queue),queueEntryLabel(entry↔ticket linkage),onQueueread once at click time for the dedupe;ListPlus/Checkiconography matches the detail page's Queue button.TicketsPage.SPEC.md("Queue the whole shown set" section, TL;DR, user story),TicketsPage.test.SPEC.md, and aFEATURES-SPEC.mdline under "Tickets" beside "Queue a ticket into the AI queue".Tests
TicketsPage.test.tsx: every shown ticket queued with title/link/priority, no agent started, button resting as "Queued" and re-arming when the set changes; already-queued tickets not queued twice (done entries don't count); claimed tickets skipped with the label counting only unclaimed; button absent when nothing is shown; button absent when every shown ticket is claimed.pnpm typecheckclean.🤖 Generated with Claude Code
https://claude.ai/code/session_019vS2EK2vVFJc3oDCtrgShR