Search for "bug tracking for agencies" and you'll find dozens of tools. Search for "bug tracking for Umbraco agencies" and you'll find almost nothing. That gap is worth addressing, because the workflow for Umbraco agency support is genuinely different from what most generic tools assume.
This post is for Umbraco developers and agency leads who build and maintain Umbraco sites for clients — and who want a proper system for handling bug reports rather than an inbox full of vague emails.
Why Umbraco Bug Tracking Is Different
Generic bug trackers are usually built with one of two users in mind: a developer filing a GitHub issue, or a technical product team member annotating a screenshot. Neither maps well to the Umbraco agency context.
Your clients aren't technical. Umbraco clients are typically marketing teams, business owners, or operations staff. They know their site isn't working; they don't know why. Asking them to install a browser extension, navigate a project board, or describe a console error is asking too much. The bug reporting process needs to be frictionless enough that a non-technical client will actually use it.
Issues span multiple layers. Bugs on Umbraco sites can originate in custom components, third-party integrations, content editor mistakes, or CMS configuration. A client reporting "the blog page looks broken" might be describing a rendering issue in a custom Razor component, a media crop that wasn't configured, or a document type field that got accidentally cleared. Good bug tracking for Umbraco means capturing enough context to triage across these layers — not just a screenshot of the front end.
Client-scoped tracking matters. If you manage five Umbraco sites, you need five separate issue streams, not one shared board where everything is mixed together. Clients shouldn't see each other's bugs, and your team needs to be able to triage per-client without manual filtering.
With that context in mind, here's how the main tools stack up.
1. Lantern — Best for Umbraco Agencies
Lantern is the only bug tracking tool with a dedicated Umbraco package, available on the Umbraco Marketplace and NuGet.
Install the package, paste your client's embed key from the Lantern dashboard into appsettings.json, and a floating bug report button appears on the frontend of the site. The critical detail: it only renders for logged-in Umbraco backoffice users. The package checks for the UMB_PREVIEW and UMB-BACKOFFICE cookies before rendering anything. Regular visitors — customers, the public — never see it. No conditional logic to maintain, no toggling around launches.
When a client with backoffice access spots an issue on their own site, the button is right there in context. They click it, record a short Loom video showing what's broken, add a title and urgency level, and submit. The issue lands in their Lantern portal, tagged to their client space, ready for your team to triage.
Each client in Lantern gets their own portal and embed key, so bugs from different Umbraco sites never mix. If you have Jira connected, issues auto-create in the right project per client. Team analytics track response and resolution times across all your clients.
Pricing is flat: $40/month for the Team plan, unlimited clients, unlimited bugs. The cost doesn't increase as you onboard new Umbraco sites.
Best for: Umbraco agencies managing multiple client sites who want a purpose-built, backoffice-aware bug reporting workflow.
2. Atarim — Built for WordPress, Not Umbraco
Atarim is a well-known visual feedback tool in the WordPress agency space. Its pin-on-page annotation system works well for design reviews and pre-launch sign-offs on WordPress sites.
The problem for Umbraco agencies: Atarim is deeply integrated with WordPress and has no Umbraco-specific support. There's no package, no backoffice awareness, and no integration with Umbraco's authentication system. You could try to embed a generic widget, but you'd lose the session-gated behaviour that makes on-site bug reporting safe to leave running in production.
Verdict: Good tool for WordPress agencies. Limited relevance for Umbraco.
3. Marker.io — Good for Technical Teams, No Umbraco Integration
Marker.io is a polished bug reporting widget that captures screenshots, console logs, network requests, and browser metadata automatically. For technical teams where users understand what console errors mean, the automatic context capture is genuinely valuable.
It doesn't have an Umbraco package or any backoffice-aware rendering. You can embed the JavaScript widget on an Umbraco frontend, but it will appear for all visitors — which means either stripping it out before go-live, or living with a "Report Bug" button that customers can click. Neither is ideal.
The per-site pricing also adds up for agencies managing multiple Umbraco sites.
Verdict: Worth considering for internal technical QA. Not designed for client-facing bug reporting on Umbraco sites.
4. Jira — Powerful, But Not Client-Facing
Most Umbraco development teams already have Jira for internal issue tracking, and it's excellent at what it does. Sprint boards, epics, custom workflows, deep reporting — Jira handles all of it.
The gap is the client-facing side. Asking a non-technical Umbraco client to log into Jira, find the right project, fill out the right fields, and submit a properly formed bug report is unrealistic. They won't do it consistently, and you'll spend time cleaning up whatever they do submit.
Jira works well as the destination for bugs — tools like Lantern integrate directly with it, auto-creating tickets per client in the right project. But as the primary intake channel for client reports, it's the wrong tool.
Verdict: Keep Jira for internal dev workflow. Use a client-facing tool for intake.
5. BugHerd — Visual Feedback, No Umbraco Package
BugHerd is one of the oldest visual bug reporting tools in the market. Install a JavaScript snippet or browser extension, and users can click directly on website elements to leave pinned feedback. It's stable, widely used, and integrates with most project management tools.
Like Marker.io and Atarim, BugHerd has no Umbraco-specific integration. The widget renders for everyone who visits the site, which creates the same problem — you either remove it before launch or accept that public visitors can see and click the feedback button. There's no mechanism to gate it behind an Umbraco backoffice session.
Per-site pricing also scales unfavourably for multi-client agencies.
Verdict: A solid tool for web agencies generally, but no Umbraco-specific advantage and no backoffice-aware widget.
6. Linear — Developer-Focused, Not Client-Friendly
Linear is arguably the best internal issue tracker for software teams right now. Fast interface, excellent keyboard navigation, tight GitHub integration, clean sprint and cycle management. Many Umbraco development teams use it for internal work.
But Linear isn't built for clients. There's no client portal, no simple intake form for non-technical users, and no concept of client-scoped issue streams. Giving a client access to your Linear workspace means giving them access to your internal tooling — which is the wrong separation of concerns. Like Jira, Linear works well as a destination for bugs, not as the channel through which clients report them.
Verdict: Excellent for internal dev teams. Not a client-facing bug tracking solution.
The Bottom Line
For Umbraco agencies, the tool shortlist is short for a simple reason: almost none of the mainstream options have any Umbraco-specific functionality.
Lantern is the exception. The dedicated NuGet package, backoffice-aware widget gate, client-scoped portals, and flat pricing are all built around how Umbraco agency support actually works. It's the only tool on this list where you can install a package, add a config key, and have a working client bug reporting system running on your Umbraco site — with zero risk of the widget showing to the public.
If you're managing Umbraco sites on support retainers and still handling bug reports by email, this is the gap worth closing first.
Install the Lantern Umbraco package:
dotnet add package Lantern.Umbraco
Create a free Lantern account →
- NuGet: nuget.org/packages/Lantern.Umbraco
- Umbraco Marketplace: marketplace.umbraco.com/package/lantern.umbraco
Questions about the Umbraco package or how Lantern fits into your agency workflow? Email hello@lanternhq.app.
Simple bug tracking for agencies. No credit card required.