Skip to main content

Release Notes — Week of 2026-10-05

Work Requests is the headline: any team can now take requests from other teams on a CRM record and track the work — stages, hand-offs, time, files — before a project exists. A typical use is sales asking presales for a technical demo or a solution design on an opportunity. Alongside it ship time tracking on any record, an Associated Records panel on every detail page, and two fixes.

Migrations to apply

Two tenant migrations ship with this release. Run them on every environment with:

npx ts-node apps/api/src/scripts/run-tenant-migrations.ts
MigrationAdds
088pipelines.scope (existing pipelines become sales); work_request_types, work_requests (numbered WR-000001…), work_request_stage_history; generic time_entries and active_timers; record_associations; documents.category. Seeds the Work Requests and Time Tracking permissions and record access on every role.
089work_requests.stage_entered_at, used for time-in-stage.
After deploying
  1. In Admin → Work Requests, create a pipeline and at least one request type (for example Technical Demo, owned by your presales team). The Request work button only lists types that have a pipeline.
  2. Users with active sessions should log out and back in to pick up the new permissions — permissions live in the sign-in token.
  3. Review any workflow that notifies presales about new opportunities — Work Requests may replace it.

Work Requests​

  • Raise a request from the new Work Requests tab on a lead or opportunity. Pick a request type, then fill in title, details, priority, needed-by date and the type's own questions.
  • Request types (Admin → Work Requests) each have an owning team, a pipeline, an assignment mode — Team queue, Auto-assign (round-robin) or Lead assigns — the record types they can be raised on, default due days, billing defaults and a request form.
  • Lifecycle — accept, assign / reassign (team lead), hand back to the queue, decline (reason required), start, move through stages, complete, cancel and reopen. A stage with an owner rule hands the request to that person automatically.
  • Work Requests page — Team Queue, My Work, My Requests and All, with search, status, type, priority and overdue filters, as a list or a board you can drag cards across. A sidebar badge counts your open assignments plus your teams' unassigned requests.
  • Request page — stage bar, details and request answers, Time, Files (technical proposals, BOQs, demo scripts) and Activity tabs, people, dates and linked records.
  • Requests follow the deal — when a lead is converted they move to the new opportunity (the lead stays linked), and when a project is created from the opportunity they are linked to it as pre-project work.

See Work Requests overview, Raising a request, Working on requests and Work Request Settings.


Time Tracking​

  • A timer (start / stop & log / discard) and manual entries on work requests, with billable flags and hourly rates defaulted from the request.
  • One running timer per user — a work-request timer can't start while a project timer is running.
  • Edit or delete your own entries; totals per person on each request.

See Time Tracking.


Associated Records​

A new panel on lead, opportunity, contact, account, task, project and work request pages lists everything linked to the record — links the record already holds (its account, contacts, tasks, project…) plus links you add with Link, each with an optional relationship label. A link shows on both records. Records you can't open are counted, never named.

See Associated Records.


Notifications, Reports and Workflows​

  • Notifications — three new types: New Work Request, Work Request Assigned and Work Request Updates.
  • Reports — new data sources Work Requests and Time Entries, including Deal Outcome (Won / Lost / Open / No deal) for questions like "win rate with vs without a technical demo". The Tasks source gains Estimated / Actual Minutes.
  • Workflows — a new Work Requests trigger module: Request Raised, Assigned, Stage Changed, Status Changed, Completed. "Owner" actions use the assignee.
  • Permissions — new modules Work Requests (view / create / edit / delete / export) and Time Tracking (view / create / edit / delete). Everyone can view, create and edit requests; delete and export are admin-only by default. Time entries default to own record access for non-admins.

See Roles & Permissions, Report Builder and Workflow Builder.


Fixes​

  • Stage assignment popup — when moving a lead into a stage with an owner rule, the popup now offers Stage Rule, Record Owner, Specific User and Team Lead, and the person you pick is actually applied (previously the choice was ignored). See Lead Pipeline & Stages.
  • Tasks report — the Status and Priority fields read the task's status and priority names (they pointed at columns that don't exist).
  • Default lead priority — setting a lead priority as the default works again (a follow-up fix to this release).

Index of changes​

  • a74c419 work requests, time tracking, associations, migrations 088/089, stage-assignment and tasks-report fixes