Read the code graph: what shipped without a ticket

Every tool shows what was planned. The code graph shows what happened, including the gap between the two: commits that reached production without ever naming a card. It belongs to the Developer plan.

What you need

The Developer plan (see pricing).
Git wired up: commit linking and tagged releases (the graph feeds on both).

1. Check the prerequisites

The most important sentence first: nobody maintains this by hand. The page derives from git and your CI: branch snapshots and merge walks. What you see is derived, not curated.

2. Open the page

The code graph lives per group, next to boards and backlog, the same visibility as everything else in the group, down to the counts.

3. Read the release spine

The backbone: every published release is a band on the timeline, with its cards, commits and PRs. "When did that go live?" becomes a glance, not a research task.

4. See the open branches

Above it, the in-flight work: open branches, what they forked from, how far ahead they are, which card they belong to. A branch open for three weeks, forked from an ancient state, stands out here (before the merge hurts).

5. Merged but not released

The in-between most tools swallow: landed, but in no release. That is the answer to "is this out yet?": merged does not mean shipped.

6. Read the no-ticket list

And the list this page exists for: commits that went to production naming no card. Not an accusation, but a finding. Some of it is Saturday night's hotfix, some the config change nobody remembers. The graph shows what the board is silent about.

One piece of honesty belongs here: a branch deleted without merging leaves no trace in git: that signal can only collect from the first snapshot onward, and the page says exactly that rather than claiming nothing was ever abandoned.

Troubleshooting

The page is empty. The feeds are missing: set up commit linking, tag releases, feed the snapshot endpoint from CI.
A release is missing as a band. It was never published: planned releases are not bands.
"Never merged" stays empty. Not a bug. See above: the signal starts with the first snapshot.

Next steps

The code graph (the feature page with the full picture).
Bind a release to a git tag.
Project management for developers.

FAQ

Does someone have to maintain the code graph?

No. It derives entirely from git and the pipeline: branch snapshots and merge walks from your CI. Nobody sorts cards or backfills versions here.

Can I see other people's private boards?

No. The group's visibility applies here too, down to the counts.

Which git hosts work?

Any whose CI can feed the snapshot and merge endpoints: they are plain HTTP calls, not a vendor plugin.

Why is “never merged” empty for me?

Because that signal cannot have a past: a branch deleted without merging leaves no trace in git. Observation starts with the first snapshot, and the page says exactly that, rather than claiming nothing was ever abandoned.

Which plan?

The Developer plan.