---
title: Developer evidence
description: Use normalized fingerprints, stacks, source context, releases, and privacy-safe reproduction evidence.
slug: developer-evidence
---

# Hand an issue to a developer

Open **Developer brief** beside the issue actions to see a compact technical handoff in the side panel. It should help a
developer identify the failing surface, reproduce the journey, and decide what evidence is still
missing without reading the entire merchant investigation.

## Copy a technical brief

Copy the brief into your developer's workflow, a ticket or a coding assistant that has access to your
code. It includes the captured technical context and observed reproduction evidence. Revenue amounts
stay in the merchant investigation rather than the technical brief. Copying is a handoff; it does
not create a Jira ticket or authorize an assistant to change your code automatically.

## Open the brief as an issue

Under **Open as an issue**, **Create Linear issue** opens Linear with the issue title and the brief
filled in. For GitHub, enter the repository as `owner/repo` (a pasted repository URL also works),
then **Create GitHub issue**. Both open in your browser with your own sign-in, and you choose the
team or labels there before saving. A long brief is shortened and links back to the full evidence in
Dozenfold. Dozenfold stores no tracker credentials; the GitHub repository is remembered only in
your browser.

## Start with the fingerprint

The fingerprint explains why occurrences were grouped. Depending on the source, it can include an
exception family and normalized message, a failed request or commerce operation, HTTP or GraphQL
status, a resource type, and a privacy-safe script or route origin.

Environment, release, browser, device, operating system, and viewport evidence show where the issue
is concentrated. Concentration is not causal lift unless a comparable baseline is available.

## Use stack and source context

When a usable stack is captured, Dozenfold displays the relevant frames and marks application and
external origins. If source maps are available, the mapped original frame and a limited source
excerpt can be shown.

Missing or unusable mapping keeps the captured stack available. Shop Owners can associate private source maps
with an immutable release from **Releases → Source maps**, either through CI automation or the
bounded manual Shopify upload fallback. Dozenfold shows only the resolved frame and limited source
context needed for investigation; it does not expose complete source files in the merchant UI.

## Reproduce with journey evidence

Use the issue’s **Reproduce** section alongside the technical handoff. It provides privacy-safe route and funnel steps,
affected sessions, and nearby error, vital, release, and friction signals. By default it cannot
reproduce DOM state, typed values, or video because Dozenfold does not collect them. When the store
has turned on error-session replay, the issue also links a masked replay of the minute before the
error and the rest of that session.

Dozenfold does not currently generate an AI diagnosis or claim an automatic fix. The handoff is
structured evidence for engineering judgment. To give the same evidence to your own AI tools, see
[AI tools (MCP)](/docs/mcp).