MCP tools for all ticket properties and per-project billability controls

This update expands the MCP interface with full access to all ticket properties and custom fields, adds per-project billability controls, and adjusts MOCO booking item naming.

Set all ticket properties via MCP

Until now, AI agents could create and read tickets over MCP but could only set a handful of properties — title, description, assignee, estimate, and type. Every other field required the web UI.

That changes now: tickets_create and tickets_update accept the full property set.

New fields for creation and updates

• Priority — low, medium, high, or critical
• Due date and planned start date
• Story points — for complexity estimation
• External reference — the customer-facing identifier
• Target environment — e.g. production or staging
• Impact level — low, medium, high, or critical
• Labels — as a list of IDs (replaces the current set; empty list removes all)
• Milestone — assign by milestone ID

Nullable fields accept null to clear the value.

Set custom fields

The new tickets_set_custom_fields tool sets organization-wide custom field values on a ticket. Supported types: text, number, date, select, and checkbox. Input is validated against the field definition — picking an invalid option for a select field returns a clear error.

Discovery tools for IDs and options

Three new query tools help agents resolve the right identifiers:

• labels_list — returns all org labels with ID, name, and color
• milestones_list — returns a board's milestones with due date and progress
• custom_fields_list — returns all custom field definitions with ID, type, required flag, and select options

tickets_get now also returns the full property set, so reads and writes are consistent.

Per-project billability controls

The project settings page under Time & Budget now includes a Billability section.

What you'll find there

1. Link to per-ticket-type billability config — opens the configuration where you set whether time entries are billable by default for each ticket type (feature, bug, epic, etc.).
2. Mark all entries as not billable — a button that retroactively sets every time entry in the project to "not billable". Useful for internal projects where you decide after the fact that no time should be invoiced.

Good to know

• Already MOCO-billed or locked entries are skipped. Spedy shows how many entries were changed and how many were skipped.
• The action requires the manage all time tracking permission.
• If MOCO is connected, the changed entries are re-pushed to MOCO in the background.

Archived projects in the time management filter

On the Manage Time page, archived projects that still have tracked time now appear in the project filter and are labelled as archived. This makes it easy to review time from completed projects.

MOCO booking items: named by external reference

The MOCO integration auto-creates a booking item (MOCO project) per ticket. Previously, this used the internal ticket number (e.g. ACME-42).

From now on, Spedy uses the ticket's external reference as the project name — the value you enter in the "External reference" property on the ticket. Typical values are customer references, PO numbers, or project codes.

If a ticket has no external reference (or only whitespace), the internal ticket number is used as before. Existing MOCO projects are not renamed; the new naming applies to newly created booking items.