Filter subtasks, open them in split view, and set a target environment

Four ticket-focused improvements in this update: subtasks can now be filtered by status and assignee, they open in a split view next to the parent ticket on wide screens, tickets get a target environment field, and the MOCO integration now reliably reconciles the billing status.

Filter subtasks by status and assignee

Tickets with many subtasks got crowded fast. Now you can narrow the subtask list right where it lives — on the parent ticket.

How it works

1. Open a ticket that has subtasks.
2. Two filters appear above the list: Status and Assignee.
3. Pick a value — the list shows only the matching subtasks.

The filters stay out of your way: a filter only appears when it has something to do. If every subtask shares the same status, the status filter is hidden. If some subtasks have no assignee, an Unassigned option is added automatically.

When a filter is active, Spedy shows a hint like "3 of 8 shown" and a Clear filters link. If nothing matches, you'll see "No subtickets match the filters."

Good to know

• Filtering is instant — no reloading.
• The progress indicator (the "done" count) is always computed over all subtasks. The filter only changes the visible list, not the overall progress.
• If a selected value disappears (for example, the last subtask in that status is gone), the filter resets to "All" automatically.

Open a subtask next to the ticket (split view)

Until now, clicking a subtask took you to its own page — and the parent ticket dropped out of view. On wide screens, that's smoother now.

On the full ticket detail page and at a screen width of roughly 1024 pixels or more, clicking a subtask opens it in a panel right next to the parent ticket. You see both at once and can resize the panel. That makes it easy to work through a list of subtasks without constantly navigating back and forth.

Prefer a new tab? Use Cmd/Ctrl-click or the middle mouse button as usual. On narrower screens and in the board's side panel, nothing changes — those still navigate.

Target environment on tickets

Tickets now have an optional target environment field. Use it to record where a ticket's change is headed — for example production, staging, or a specific release.

How to set it

1. Open a ticket and go to Properties.
2. In the Target environment row, enter a value (free text, e.g. production).

Environment-aware suggestions on PR merge

When a pull request linked to the ticket is merged, Spedy knows the target environment and includes it in the status suggestion. Instead of just

Pull Request #42 was merged. Should the ticket be set to "Done"?

you'll read

Pull Request #42 was merged – target environment production. Should the ticket be set to "Done"?

So you can see where the code went before you confirm the status. Note: it stays a suggestion — the status never changes on its own. The field builds on the existing status-suggestion feature (Pulse); if that's turned off, you can still use the target environment as a plain info field.

MOCO: reliably reconcile the billing status

If your team uses the MOCO integration for time tracking and billing, Spedy now keeps the billing status of time entries up to date more reliably.

Previously, the "billed" signal came in only through MOCO webhooks. If a webhook was lost — for instance during bulk invoicing — a time entry stayed "billable" in Spedy even though it had long been invoiced in MOCO.

The new reconcile pulls the billing status straight from MOCO and brings Spedy back in line:

• It runs automatically every hour in the background — nothing for you to do.
• Under Settings → Integrations → MOCO, you can also trigger it any time with Reconcile billed status. Spedy then shows how many entries were marked billed or reverted.
• The MOCO sync overview now also shows the number of billed time entries.

Entries marked "not billable" are never touched.