Datum

Docs → Trailkeeper

Documentation · Jirav2.6.1

Trailkeeper docs

Trailkeeper shows who changed what on a Jira issue, in a Trailkeeper — Change History panel on the issue view, and adds a Trailkeeper Reports page under the Apps menu for cross-project audit reports, a personal-data scan, deleted issues and bulk revert, plus a Recent changes dashboard gadget. It runs entirely on Atlassian Forge.

Getting started

Before you install

  • Jira Cloud. A Jira admin installs the app from the Atlassian Marketplace and approves its scopes.
  • Anyone who can browse an issue can open its change-history panel. Reports only include issues the person running them can already browse.
  • Restore issue (Standard plan) is limited to Jira admins and admins of the deleted issue's project, who also need Jira's own Create issues, Add comments and Transition permissions, because the restore runs as them.
  • Revert (Standard plan) runs as the person who clicks it, so Jira's Edit and Transition permissions on that issue apply.

Install and first use

  1. InstallInstall Trailkeeper from the Atlassian Marketplace. From then on it keeps a last-known copy of every issue that is created, edited, commented on or deleted.
  2. Open the history panelOpen any Jira issue and open the Trailkeeper — Change History panel. It lists each field change — field, old value, new value, who and when — newest first, with status, priority and custom-field names shown instead of raw ids.
  3. Search and exportType in Search to filter by field, value or author. Click Export CSV, then copy the result into Excel or Google Sheets.
  4. Check deleted issuesOpen Apps → Trailkeeper Reports and choose the Deleted issues tab, then List deleted issues. You see who deleted each issue and when, most recent first. If a sub-task or child issue was deleted, its parent's history panel shows that too.
  5. Run audit reports (Standard)On Trailkeeper Reports, use the Change report tab with a JQL query, or the User activity tab with a JQL query plus an author, and click Run. Export the result with Export CSV, download it as a file, or Save as PDF through your browser's print dialog.
  6. See sprint history (Standard)On the Change report tab, set Fields to Sprint changes only and click Run. Each row shows an issue being added to, removed from or moved between sprints: the sprint names before and after, who did it and when. Exports include the same rows. Sprint changes can't be reverted.
  7. Scan for personal data (Standard)Open the Personal data scan tab, enter a JQL query and click Run. Trailkeeper looks through the old and new values in those issues' change history for email addresses, payment card numbers and IBANs, and lists the issue, field, kind of data, who made the change and when. Matches are always masked (for example j***@example.com or **** **** **** 1234) on screen and in exports.
  8. Add the Recent changes gadgetOn a Jira dashboard, click Add gadget and pick Trailkeeper — Recent changes. In its Edit settings choose One project or Issues matching a JQL, an optional Field and a Time window (last 24 hours, 7 days or 30 days), then click Save. The deleted-issue count for the window is free; the table of latest field changes (issue, field, old → new value, who, when) needs the Standard plan.
  9. Recover a deleted issue (Standard)On the Deleted issues tab, click View to see the issue's last-known content. Admins can click Restore issue to create a new issue from it, or use Export for Jira import to get a CSV for Jira's own CSV importer.
  10. Ask RovoIf your site has Rovo, open the Trailkeeper Audit agent or ask Rovo chat Who changed the priority on PROJ-7? It answers with the field history of an issue and the log of deleted issues (projects you can browse; Jira admins see all). On Standard it also summarises who changed what across issues for a JQL and date range. It never reverts or restores; use the panel or Reports page for that.

Configuration

Audit retention

On the Standard plan, the Deleted issues tab has an Audit retention (days) field. Enter a number of days and click Save policy. It sets how long the per-issue audit event log is kept. The default is 90 days; any value is clamped to between 1 and 3650 days.

Restoring deleted issues

Restore issue creates a new issue in the same project, as you, with the captured summary, description, fields and comments, then moves it to its old status if the workflow allows. Jira gives it a new key. A note on the new issue lists anything that couldn't come back.

Attachment files and the issue's change history can't be restored. Trailkeeper keeps only each attachment's name, size, uploader and upload date, and lists them in the restore note so someone with the original file can re-attach it.

To restore several issues, click Select all shown (up to 200 at a time), then start the bulk restore. It runs in the background with a progress view. Each deleted issue can be restored once.

Reverting changes

On the Standard plan, each row in the history panel has a Revert button that sets that one field back to the value it had before the change. Trailkeeper re-reads the change from Jira before applying it, and Jira's history shows you as the editor.

The Bulk revert tab on Trailkeeper Reports undoes changes made by one person or automation in a time window. Enter Issues (JQL), Changes by, From and To, click Preview changes, check the list, then confirm with Yes, revert. Fields someone else changed afterwards are marked as a conflict instead of being overwritten.

When Trailkeeper writes to Jira

Trailkeeper changes Jira only when someone clicks Restore issue or Revert (single or bulk), and always as that person. Listing, viewing and exporting never change Jira. Nothing is written automatically.

Language

Available in English, German, French and Spanish. The app follows each person's Jira language setting; Rovo answers, exports and comments the app posts stay in English.

Free vs Standard

Plans and prices below are read from the same pricing file the app uses. Atlassian bills per user per month on your site's user tier, and the price per user steps down at larger tiers. See all pricing.

Free

Free

  • Full field-change history per issue (status/priority/custom-field names resolved)
  • Basic history search
  • CSV export (up to 500 rows)
  • Deletion log: who deleted which issue, and when (since install)
  • Deleted sub-tasks and child issues shown on the parent issue

Standard (Audit & Compliance)

$0.90 / user / month

Free for sites up to 10 users. 30-day free trial.

  • Cross-project change reports (JQL-scoped)
  • User-activity audit trail across projects
  • Uncapped CSV export plus Excel (.xlsx) downloads
  • Continuous change capture (snapshot + retention-windowed event log)
  • Deleted-issue recovery: full last-known snapshot incl. description, comments, reporter, dates, components, versions and custom fields (since install)
  • One-click restore of a deleted issue (Jira or project admins; runs as the user)
  • Revert a single field to its previous value from the issue history
  • Bulk restore (up to 200 deleted issues per run, with progress)
  • Bulk revert: undo one user's or automation's changes in a time window (preview first)
  • PDF export via print view
  • Rebuild export: deleted issues as a CSV for Jira's own importer
  • CSV file downloads
  • Compliance export of an issue's full captured audit trail
  • Configurable audit retention policy (1-3650 days)

Limits

  • Free plan: CSV export from the history panel is capped at 500 rows. Standard plan exports are uncapped.
  • Cross-project reports and the personal-data scan cover up to 1,000 issues matching the JQL per run. A scan lists at most 5,000 matches; narrow the JQL if it says there are more.
  • The personal-data scan reads Jira's change history only: it doesn't scan current field values that were never changed, comments or attachments. Card numbers must pass the card-network prefix and Luhn checks, and IBANs the country-length and mod-97 checks; email addresses are matched by pattern. It finds likely personal data, not all of it.
  • The Recent changes gadget reads the 50 most recently updated issues in its scope and shows the newest 20 field changes; open Trailkeeper Reports for the full list.
  • The deleted-issues list shows the 5,000 most recent deletions; a rebuild export for Jira's importer takes up to 500 issues at a time.
  • Bulk restore handles up to 200 deleted issues per run; a bulk revert preview covers up to 300 field changes.
  • Deleted-issue content and the audit event log exist only for issues created, changed, commented on or deleted after Trailkeeper was installed.
  • Captured content is capped to fit Forge storage: description 20,000 characters, the latest 50 comments (4,000 characters each), 80 custom fields (1,000 characters each) and 100 attachment names. Longer values are shortened, and the deleted-issue view says so.
  • Audit retention can be set from 1 to 3650 days (default 90).
  • There is no server-generated PDF or Excel file: PDF uses your browser's print dialog, and CSV opens in Excel or Google Sheets.

Data & privacy

What Trailkeeper stores

  • Everything is kept in Forge hosted storage, isolated to your Jira site's install. The manifest declares no external permissions, so no data is sent to servers outside Atlassian.
  • A last-known snapshot per issue: summary, status, priority, type, assignee, reporter, labels and parent, and — for full content — description, comments (author and date), created and due dates, resolution, components, fix and affects versions, time tracking, custom fields and attachment names.
  • A per-issue audit event log of field changes (field, old and new value, the Atlassian account id of who made the change, and when), pruned to your retention window on every write.
  • A record of each deleted issue: who deleted it and when, and whether it has been restored.
  • Your retention setting, and progress records for bulk restore and bulk revert jobs, which expire after 7 days.
  • Not stored: attachment files. CSV and PDF files are made in your browser.
  • Once a week Trailkeeper reports the Atlassian account ids it holds to Atlassian's personal data reporting service; for closed accounts it replaces the id with an anonymous marker.

Trailkeeper runs on Atlassian Forge. Data it stores sits in Forge hosted storage for your site, which Atlassian pins to your product's region. See Trust & security, the Privacy Policy and the DPA.

Permissions (scopes)

ScopeWhy Trailkeeper needs it
read:jira-workRead issues, their change history and comments to show the history panel, run reports and capture snapshots.
write:jira-workCreate a restored issue (with its comments and status) or set a field back on Revert. Used only when someone clicks those buttons, and always as that person.
storage:appKeep issue snapshots, the audit event log, the deletion log and your settings in Forge hosted storage.
report:personal-dataReport the Atlassian account ids it stores to Atlassian each week, so closed accounts can be anonymised.

FAQ & troubleshooting

Does the personal-data scan change or remove anything?

No. It only reads and lists. It shows where personal data appears in issue history so you can deal with it in Jira; the full values are never shown or exported by Trailkeeper.

Can Trailkeeper show issues that were deleted before I installed it?

No. Once Jira deletes an issue, its history is gone from Jira too. Trailkeeper can only show and restore issues it captured — those created, changed, commented on or deleted after install.

How far back does the history panel go?

The panel reads Jira's own changelog for the issue, so it shows what Jira has recorded for that issue. The audit event log that Trailkeeper stores itself is kept for your retention window (90 days by default, up to 3650).

A deleted issue only shows its summary fields. Why?

Full content (description, comments, custom fields and so on) is captured when an issue is created, edited or commented on. Issues captured only by an older Trailkeeper version, and not changed since, have summary fields only.

Does restoring bring back the same issue key, attachments and history?

No. Restore creates a new issue with a new key. Attachment files and the change history can't be restored; the restore note lists the attachments' names, sizes, uploaders and dates instead.

Why can't I see a deleted issue that a colleague can?

The deleted-issues list only shows issues from projects you can browse. Jira admins see all of them.

Why is the Restore issue button missing or refused?

Restore needs the Standard plan and is limited to Jira admins and admins of that issue's project. Each deleted issue can be restored only once; a restored one shows the key it was restored as.

Why does a bulk revert row say Conflict?

Someone else changed that field after the change you are undoing. Trailkeeper leaves those fields alone rather than overwrite the later change.

Does any data leave Atlassian?

No. Trailkeeper runs on Atlassian Forge, stores data in Forge hosted storage for your site, and declares no external network access. Files you export are created in your browser.

Changelog

Every release and what changed: Trailkeeper changelog.

Getting help

Email support@datadir.co with your site URL and what you saw. Our target is a first response within 1 business day. See Support for what to include, and Status for known issues.