2026-06-03 Weekly Deployment Changelog

Summarized the changes since the May 27, 2026 noon deployment, including customer media uploads, Help Desk updates, ticketing cleanup, and operational fixes.

2026-06-03 Weekly Deployment Changelog

This release covers the changes merged after the Wednesday, May 27, 2026 noon deployment. The biggest themes are easier customer media collection, a new first-party Help Desk experience, removal of the old ticketing module, and a set of stability fixes around CPQ, calendar events, work-order photos, Twilio requests, and deployment.

Highlights

  • Added customer upload links so staff can request project photos and videos without requiring the customer to log in.
  • Added the new Help Desk experience, including first-party Inertia views, sidebar navigation, permissions, and host-app actions.
  • Connected Help Desk tickets to customer media collection with a Collect Media action that sends upload links to project or customer requesters.
  • Removed the legacy Ticketing module and related service-ticket report pieces now replaced by the new Help Desk stack.
  • Improved Parable item rendering in project reports so configured options appear more reliably, with a fallback when the Parable summary is unavailable.
  • Added weekly deployment automation and updated vulnerable dependencies.

What End Users Will Notice

Customers can send media without an account

Staff can now create a customer upload link from project-facing screens and email it to the customer. The customer can open the public, tokenized link, upload photos or videos, and see a success or expiration page without signing in to Tempr.

Upload links expire after 24 hours and accept up to 200 MB of photos or videos per link. Project-facing updates are broadcast when the customer opens the link and when files are received, so staff have better visibility into whether requested media is on the way or already attached.

Help Desk is now available in the main app

The new Help Desk is registered in the main sidebar for users with the right permissions. It uses the Escalated helpdesk package with Tempr-owned layout, routing, authorization gates, and Inertia views so agents can work tickets from inside the normal application shell.

The Help Desk also includes a Collect Media action. When an eligible project or customer ticket needs photos or videos, staff can trigger that action and Tempr will create a customer upload link tied back to the ticket and notify the customer.

Legacy ticketing has been retired

The old Ticketing module, old ticket states, old ticket invite notification, and legacy ticket database migration were removed. Calendar events no longer accept or display links to those legacy tickets, and old service-ticket report fragments were cleaned out.

Project and report output is cleaner

Parable line items now render a dedicated report view that pulls summarized configuration data when available. If the Parable summary call fails or no grouped summary exists, the report falls back to the raw configuration values so staff still see useful product details.

Work-order photo uploads now create a project photo record in addition to media-library storage, improving consistency for tools that read project photos from the application database.

Smaller workflow fixes

Purchase orders can now move from Sent to Transmitted, covering an additional real-world status path. Twilio signature verification now handles form-encoded request bodies more reliably. A small lead-form message was corrected, and several feature tests were updated to match current app behavior.

Operational And Technical Notes

  • Added a weekly deployment GitHub Actions workflow.
  • Added config/nav.php to centralize main sidebar navigation.
  • Updated Composer and npm lockfiles for CVE-related dependency updates.
  • Adjusted Vite and Escalated frontend assets for the new Help Desk views.
  • Added focused tests for customer upload links, Help Desk custom actions, Parable report rendering, and related stability fixes.

Overall Impact

This deployment moves more customer follow-up and support work into first-party Tempr workflows. Staff get a clearer path for collecting customer media and working Help Desk tickets, while the system sheds the old ticketing module and receives a round of reliability updates in reporting, integrations, and deployment automation.