Epic Grouping, Bulk Actions in the Backlog, and Opus 4.7

This week is more of a polish release: a bunch of things that were painful in day-to-day work now go faster. Attach stories to their Epics, group the backlog by Epic, clean up large ticket piles in one go — and in the runner, Claude Opus 4.7 arrives as the new default.

Connect Epics and stories

Epic has existed as a ticket type for a while, but the actual link from an Epic to its stories was something you had to improvise with labels, search, or the title. No more.

• Every ticket now has an Epic field. Open the ticket properties, start typing a title or ticket ID, and pick the Epic you want. Only tickets of type Epic on the same board are selectable.
• Open an Epic and you'll find a Tickets in this Epic panel at the top. It lists every attached story, jumps you into any of them with one click, lets you add more tickets via search, and lets you remove a story from the Epic without deleting it.
• The Issues Hub gets a new Epics filter: pick one or several Epics and the list narrows down to just their stories — useful for tracking the progress of a large initiative that spans multiple boards, from a single place.

Worth noting: Epics and subtasks are two different things. Stories under an Epic stay first-class tickets with their own status, assignee, and priority — they don't "live inside" the Epic the way subtasks live inside a parent.

Group the backlog by Epic

Almost as a side effect, the backlog is now easier to scan. A new Group by dropdown at the top has two modes:

• None — the flat list you're used to.
• Epic — tickets are listed under their parent Epic, and standalone tickets land in a separate No epic group.

Your choice is remembered per board. When you come back later, the backlog looks the way you left it.

Bulk actions: backlog and Issues Hub

When a hundred bugs pile up on a board, or you want to tidy up after a big release, clicking through tickets one by one isn't a great use of anyone's time. There's now a shared bulk action toolbar available both in a board's Backlog and in the cross-board Issues Hub.

How it works:

1. Select tickets with the per-row checkbox. A Select all checkbox in the header toggles the whole visible list.
2. As soon as one or more tickets are selected, the toolbar slides in at the bottom of the screen.
3. Available actions:
   • Change status — moves all selected tickets to the same status.
   • Change assignee — reassigns all of them to the same person, or clears the assignee.
   • Delete — soft-delete after confirmation.

The guardrails:

• Max. 500 tickets per action. Above 50 selected, Spedy asks you to confirm once before the change goes through — so a misclick can't wipe out a board.
• Delete is a soft delete, not a one-way operation. Admins can make deleted tickets visible again if needed.
• In the Issues Hub, your selection can include tickets from multiple boards. Tickets on boards you don't have access to are silently skipped and returned as skippedIds — a broad selection never reaches past your board permissions.

Runner: Claude Opus 4.7 is the new default

Anthropic released Claude Opus 4.7. The default pipeline now uses it for the Planner stage — the stage that takes a ticket and turns it into the implementation plan, and the one that benefits the most from the stronger reasoning.

What this means for you:

• New pipelines use Opus 4.7 automatically.
• Existing stages keep the model you already picked — nothing on a live setup changes without your say-so.
• The model selector still lists Haiku 4.5 and Sonnet 4.6, and now also Opus 4.7 — strongest plus Opus 4.6 — previous generation for teams that want to stay on the older model.

Switching to 4.7 costs nothing extra — just flip it in the stage config.

Two smaller things

Finally, two improvements aimed mostly at automation and agent users:

• New MCP resource attachment://{id} — MCP agents (for example, Claude running a routine) can now load ticket attachments as a real resource: images, PDFs, text. Until now they only saw an attachment count. Binary files up to 10 MB come back as base64, text files as text. Access is gated by the same board permissions as the rest of Spedy.
• Read agent executions via PAT — the read endpoints of the Agents API (GET /agents/executions/:id, …/specification, /crews, /crews/:id, /tickets/:id/executions) now accept a Personal Access Token in addition to a session cookie. External integrations can poll the state of an agent run without holding a session. Starting, cancelling, and applying a spec stay session-only on purpose.

Try it now

• Attach an Epic: open a ticket → ticket properties → Epic → search and pick.
• Group the backlog: open a board → Backlog tab → Group by dropdown → Epic.
• Bulk actions: select tickets with checkboxes in the backlog or Issues Hub → use the toolbar at the bottom → change status, change assignee, or delete.
• Opus 4.7: board settings → Runner → edit a pipeline stage → Model: Opus 4.7.