Datum

Apps → Trailkeeper

A Datum app for Jirav1.0.0

Trailkeeper

See who changed what, recover deleted issues, and export audit-ready reports — data never leaves Atlassian.

Field historyTrailkeeper · SPT-204
Status To Do → In Progress 2h ago
Assignee Unassigned → Sam R. 1d ago
Points 3 → 5 3d ago
Who changed what, and when — the trail Jira's activity view drops.

The problem

When a field changed, who changed it, and what was the old value? Jira's native activity view drops most of the detail — history gets collapsed, search is basic, and there's no clean answer for 'what actually happened to this issue'. Audits, debugging and trust all suffer.

How it works

1

Read the real changelog

Trailkeeper reads the issue changelog API and keeps the full field-change history — who, what, when, from → to — including changes Jira's native view drops.

2

Search the history

Find the change you need with basic history search across an issue's life — no more scrolling through collapsed activity.

3

Export when you must

On Standard, take the same history cross-project, break it into user-activity audits, and export to CSV/Excel when compliance asks.

A Datum app

the promise

Like every Datum app, Trailkeeper is Forge-native and runs inside your own Jira site — free for up to 10 users, with a single honest paid plan after. No separate sign-up, no data leaving your tenant. Why Datum →

Screenshots

Click any shot to view it full size.

FAQ

What does the free tier include?

Full per-issue field-change history and basic search, free up to 10 users.

Does it capture deleted issues?

Standard adds a deleted-issue recovery view, so history survives even when the issue itself doesn't.

How does it run?

On Forge, reading Jira's own changelog data in your tenant — nothing is copied off-site.

Works well with

Explore all Datum apps →

Guides

Best Jira audit log & history apps (2026) A side-by-side look at the best Jira audit log, change history and deleted-issue recovery apps in 2026 — what each does, who it fits, and how they're priced. How to see what a user changed in Jira Jira's activity views won't show everything one person changed across projects. Here's how to get a per-user change trail for audits and offboarding. How to set up a Jira audit trail for compliance Compliance needs a reliable record of who changed what and when — retained and exportable. Here's how to set up a Jira audit trail that stands up to an auditor. How long does Jira keep issue history? Jira keeps an issue's change history only as long as the issue exists — delete it and it's gone. Here's how to keep history that outlives deletions. How to export Jira issue history to CSV Jira's issue history lives in the activity tab with no export button. Here's how to get field-change history out as CSV for audits and reporting. How to find out who deleted a Jira issue Jira's admin audit log shows who deleted an issue and when — but not its contents. Here's how to find the person, and keep the data a deletion takes. How to recover a deleted issue in Jira (and what to do before it happens) Jira Cloud has no one-click undelete for a single issue. Here are your real options after one is deleted — and how an audit trail protects you next time. Jira audit log vs issue history — what's the difference? Jira's audit log and issue history — two change records teams confuse. What each covers, where both fall short, and how to see field changes across issues.

Get Trailkeeper

Free for up to 10 users, with one honest paid plan after. See pricing →