Bug Tracking for Umbraco Development Agencies: Native Backoffice Integration, No Workarounds

Umbraco agencies work at a different layer of complexity than most web shops. Your clients aren't just managing content — they're editors working inside a custom backoffice built around their specific document types, content trees, and publishing workflows. When something breaks, it might be in the front-end render, the backoffice editor, a Data Type configuration, or a surface controller. Pinpointing it from a client's email description is rarely straightforward.

The good news: Umbraco agencies have a native option. Lantern is the only bug tracking tool with a dedicated Umbraco NuGet package.

The Bugs Umbraco Agencies Deal With Most

Umbraco development agencies see a distinct set of recurring issues:

Backoffice editor bugs — a content type field doesn't save correctly, a media picker throws an error, a rich text editor loses formatting on save
Front-end rendering issues — a Razor template renders incorrectly for certain content structures, or a partial view breaks when a property is null
Surface controller and form errors — form submissions fail silently or redirect incorrectly; validation errors aren't displayed as expected
Permission and workflow bugs — editor roles can access content they shouldn't, or publishing workflows don't trigger correctly
Environment-specific issues — a bug that only appears in the production environment, not locally or on staging

Many of these are only visible to logged-in backoffice users — which is exactly why a bug reporting tool needs to be CMS-aware.

Native Umbraco Integration: What It Actually Means

Generic bug tracking tools require clients to open a separate tab, navigate to a bug reporting portal, and manually describe what they saw in the backoffice. By the time they get there, they've lost context — and you get a description of the symptom, not the state.

Lantern's Umbraco package (Lantern.Umbraco, available on NuGet) renders the bug report widget directly inside the Umbraco backoffice, visible only to authenticated backoffice users. The widget detects the Umbraco session and shows only to logged-in editors — completely invisible to front-end visitors.

Install via NuGet:

dotnet add package Lantern.Umbraco

Add your embed key to appsettings.json and the widget appears in the backoffice. That's the full setup.

How Lantern Works for Umbraco Agencies

Widget in the Umbraco backoffice. Clients see the report button while they're editing content, managing media, or navigating the content tree. They find a bug, click the button, and report it without leaving the backoffice.

Loom video walkthroughs. For backoffice bugs — where the sequence of clicks matters — video is invaluable. The client records exactly what they did and what happened. You see the content type, the field, the error. No guesswork.

Automatic context capture. Browser, OS, and URL are captured at submission. For Umbraco, the URL often tells you which section of the backoffice the client was in, which is useful context.

Per-client scoped portals. Each client sees only their issues. You see all clients in one dashboard.

Pricing

The Team plan at £30/month covers unlimited clients and team members — right for Umbraco agencies managing multiple client installations. If you're a solo Umbraco developer, the Individual plan at £12.50/month covers up to 5 clients with a free trial.

Detailed setup guide: Umbraco bug tracking setup

Start your free trial →