Bug Tracking for Umbraco Cloud Agencies: Handle Client Bugs Across Environments

Umbraco Cloud changes the support workflow for agencies. You're not managing a VPS or a self-hosted IIS installation — you're working with Umbraco's managed cloud infrastructure, environment slots (Development, Staging, Live), and git-based deployment pipelines. When a client reports a bug, the first question is often: which environment? Which deployment? Was this introduced in the last push?

That context — the environment, the deployment state, the URL — is exactly what a text email doesn't include.

Umbraco Cloud Bug Patterns

Agencies hosting clients on Umbraco Cloud see a specific set of recurring issues:

Environment mismatch bugs — something works on Development or Staging but breaks on Live after deployment, often due to configuration differences or missing environment-specific settings
Post-deployment regressions — a content deployment or code push introduces a regression that clients notice before the agency does
Backoffice-specific issues — Umbraco Cloud's shared backoffice infrastructure occasionally has version-specific quirks in the editors, workflow tools, or media library
CDN and caching issues — cached assets serving stale content after a deployment, visible to clients and their users

Many of these are only reproducible when you know exactly which environment the client was in, which URL they were on, and what browser they were using — none of which arrives in a typical bug email.

The Environment Context Problem

Umbraco Cloud agencies frequently spend the first part of any bug investigation establishing basic facts: "Was this on your Live site or Staging?" "What's the URL?" "Did you clear your browser cache?" These aren't difficult questions, but each one adds a round-trip delay.

A bug tracking tool that captures the URL automatically — including the environment subdomain — eliminates this step entirely. You open the report and immediately know whether the client was on .umbraco.io (Staging) or the production domain.

How Lantern Works for Umbraco Cloud Agencies

Installed via NuGet, configured per environment. Lantern's Umbraco package (Lantern.Umbraco) installs the same way on Cloud as on self-hosted. Add your embed key to appsettings.json in each environment where you want the widget to appear. You can enable it on Live, Staging, or both depending on your workflow.

dotnet add package Lantern.Umbraco

Widget visible only to backoffice users. On Umbraco Cloud, the widget detects the Umbraco backoffice session and shows only to authenticated editors — not to front-end visitors on the production domain. Client editors see the report button in the Cloud backoffice; the public doesn't.

URL captured automatically. The environment URL is captured with every submission, so you immediately know whether the bug is in Staging or Live without asking.

Loom video for reproduction. Backoffice bugs and post-deployment regressions often require seeing the sequence of actions — not just the end state. Video replaces the "steps to reproduce" email thread.

Per-client dashboard. All open issues across your Umbraco Cloud clients in one triage view.

Pricing

Team plan: £30/month for unlimited clients — the right fit for agencies managing multiple Umbraco Cloud projects. Individual plan: £12.50/month for up to 5 clients with a 14-day free trial.

Full setup walkthrough: Umbraco bug tracking

Start your free trial →