Every feature

There is one plan and every feature on this page is in it. The plan is free for up to 10 users.

Works with

Where it appears in Jira

Change history reports

The Changes tab. See Reports and the explorer.

Choosing what to load

• Projects, with the projects you last used remembered in your browser.
• Date presets (today, yesterday, this or last week, this or last month, last 7, 30 or 90 days) or a custom range.
• Work item keys, typed or pasted, with any key that isn’t one, or that you can’t see, named before the report runs.
• A Jira saved filter, sprints (open and closed) and your own JQL on top.
• JQL checked against Jira’s own parser as you type, with Jira’s error shown under the box.
• Everything compiled into one JQL query, shown beside Run so you can copy it into Jira.
• Up to 25,000 work items and 150,000 changes per report, with the limit you choose (1,000, 5,000, 10,000 or 25,000).
• Progress while it loads, Cancel at any point, and an automatic wait-and-retry when Jira asks the app to slow down.

Reading the result

• Activity view: one row per field change (when, work item, field, from, to, by).
• Table view: one row per change moment with fields as columns, frozen When, Work item and Updated by columns, sideways scrolling and Jump to column.
• Columns manager: pick fields, ordered by how often they changed, with counts, Select all and Select none.
• Sorting on any column, with shift-click for up to five sort keys, and natural key order (OPS-9 before OPS-10).
• Group by work item, with each item’s summary and change count.
• Badges: Created (a row for each item’s creation, which Jira’s history leaves out), Latest, New and BULK (the same field changed on 5 or more work items within 10 seconds by one person or automation).
• Word-level diffs for summaries, descriptions, environment, comments and long text fields, cut to the changed parts with Show full text.
• List fields (labels, components, versions, sprints, watchers) shown as added and removed chips.
• Time-tracking fields shown as durations with the difference, for example 30m → 2h (+1h 30m).
• ⟷ to step through one field’s history on one work item, change by change, with the arrow keys.
• A preview of any work item when you hover over its key.
• Fields named as Jira names them (Status, Remaining Estimate, your site’s name for each custom field).
• Changes that changed nothing (for example Backlog → Backlog) hidden and counted, with Show them.
• A summary line counting changes and work items, repeated for screen readers, and a warning whenever a load stopped at a limit.
• An empty report explains which step removed everything: the JQL, the dates or a named filter.

Filtering what’s loaded, instantly

• Changed by, with a Me shortcut. Click a person’s name in the results to show only their changes.
• Changed by group, for up to 20 Jira groups.
• Field.
• Search over key, summary, field, old value, new value and author, with quoted phrases, a match count and highlighted matches.
• Bulk changes only.
• Transitions on any field: In Progress → Done, → Done, In Progress →, ~prog → ~done, several at once.
• Exclude…: not changed by, not these fields, and text to exclude.

Saved views and sharing

See Saved views and sharing.

• Save the whole report: scope, dates, every filter, the view, the columns, the sort and the grouping.
• Private views, or views shared with everyone who can use the app.
• Update, Save as new (to copy anyone’s view) and Delete, with editing rights enforced by the app’s backend.
• Copy share link: a link that opens the identical report and runs it straight away, for anyone, under their own permissions.
• Comment on a work item: post a report’s link and description as a comment, so Jira notifies the people watching it.
• Reset to the default report.

The Reports tab

See The Reports tab.

• Time in value: total and average time in each value of any field (Status by default), and a row per work item and value with the time and how many times it was entered.
• Change counts: changes by field, by author and by work item.
• Status over time: how many work items held each value at the end of each day, as a stacked chart, grouped by week beyond 120 days.
• Durations in the time format your administrator sets.
• The chart downloads as SVG or PNG.

One work item’s history

The History+ tab, or the Change history panel. See Tracking and Revert.

• Every field change on the work item, with diffs, chips and durations as in the explorer.
• Comment history: every version of every comment.
• Viewed by: who opened the work item and when.
• Export that item’s history to CSV, Excel or PDF.
• Revert changes from the same list.
• Field changes and comment history stay available without a subscription.

Deleted work items

The Deleted items tab. See Deleted items.

Capture

• On from the moment the app is installed, with nothing to switch on.
• A snapshot of each work item whenever it is created or changed: core fields, rich-text description, custom fields, fix and affects versions, environment, original estimate, security level and subtask keys.
• Who deleted it and when, recorded when it is deleted.
• full or partial capture shown on every row, with the number of custom fields captured.
• Backfill: a one-off job that takes a full snapshot of every existing work item the app can read, in the background, page by page. A work item at a security level that leaves out the app can’t be snapshotted, so if it is deleted it may not be captured at all, or only partly. A partial capture is shown only to Jira administrators.
• Retention of 1 to 365 days (90 by default), after which records expire on their own.
• Capture keeps running if the subscription lapses.

Finding a deleted item

• Filters for projects, deleted by, deleted from and to, a search over key and summary, and Hide already restored.
• Sorting by date, key or summary, with each subtask kept under its deleted parent.
• The person who deleted it, by name.
• Export the list to CSV or Excel.
• Items listed only for people who can browse the project, and, for an item in an issue security level, only for people Jira confirms are in that level. Jira administrators see every secured item; anyone else gets a short note, naming nothing, when something was left out.

Restoring

• A preview first, built against the target project’s create screen, listing what comes back and what doesn’t, with the reason for each.
• Summary, description (with a line saying where it was restored from), type, priority, labels, components, assignee, due date, parent, custom fields that still fit and the original estimate.
• The old status, restored through the workflow after creation.
• Subtasks deleted with the parent, restored under the parent’s new key, each in its own old status.
• Captured comments re-posted on the new work item, up to 40, each naming its original author and date.
• Edit before restoring…: change the summary, description, labels or target project for this restore.
• If Jira refuses the full set of fields, the work item is still created with its core fields, and the result says so.
• A result screen with the new key, the status, how many custom fields and comments came back, what was skipped and why, and each subtask’s outcome.
• Each item can be restored once, with a guard against a second tab creating a duplicate.

Revert

See Revert.

• Put one field back, or select a whole bulk edit or automation run and revert it together.
• Revert from the Changes tab or from a work item’s history.
• A dry run first: each change marked Ready, Conflict (changed again since, with the current value) or Not revertible (with the reason).
• Every work item read again just before it is written, so an edit made while the preview was open is never overwritten.
• Supported fields: summary, text, rich text, labels, users, priority, type, parent, select lists, dates, numbers, components, versions, multi-selects, sprints and status (through a workflow transition).
• Writes run as you, so Jira’s history names you and your edit permissions and workflow rules apply.
• A results table (Success, Failed, Skipped) and a CSV of the plan or the outcome.

Exports

See Exports.

• CSV, Excel and PDF of the change history, from the Changes tab and from a work item’s history.
• Every row on screen after filtering and sorting, not just the current page.
• UTC time, local time and the UTC offset on every row, correct either side of a daylight-saving change.
• Display values and Jira’s raw values (in CSV), and the field ID.
• An Excel Settings sheet recording the JQL, the report in words, the export time, the row count and the time zone.
• Excel formatting: bold frozen header, autofilter, shaded old and new values, readable column widths.
• CSV delimiter of comma, semicolon or tab; UTF-8 with a byte-order mark; formula-injection protection.
• Built in chunks with a progress count and Cancel from 5,000 rows, tested at 250,000 rows, with Excel continuing onto further sheets past 1,048,575 rows.
• PDF as an A4 landscape table with the query as its subtitle.
• Reports tab exports: CSV, Excel (one sheet per table, durations also as hours you can sum) and PDF.
• Deleted items list and Security scanner findings to CSV (and the deleted list to Excel).
• Files are built in your browser and saved to your machine.

Signed exports

See Signed exports.

• Tick Sign it and give a reason before exporting CSV, Excel or PDF from the Changes tab.
• The file’s SHA-256 fingerprint, who exported it, when, the reason, the query and the report in words, recorded on your site.
• A .export-record.txt downloaded beside the file.
• Verify a signed export on the admin page: drop the file in and see Unaltered with its record, or No record for this file.
• The file itself never leaves your browser.

Scheduled reports

See Scheduled reports.

• A project and a period, or any saved view, run every day, week or month at a chosen UTC hour.
• Delivered as a CSV or Excel attachment on a work item you choose, with a comment summarising the run (counts, the five latest changes and the file name), so Jira notifies everyone watching it.
• Each schedule limited to the projects its creator could browse when it was saved, and says so in every delivery.
• Run now, the last run’s outcome in the list, and Delete with a confirmation.
• Up to 100 schedules per site.

Comment history and viewer history

See Tracking.

• Comment history: each comment’s original text, every edit (up to 50 versions) and its deletion, with who and when.
• Viewer history: who opened a work item and when, the last 500 views per item, one per person every 10 minutes.
• Both on by default, each switchable site-wide, with a list of projects to exclude.
• Erase captured tracking data: remove comment versions, view records or both, for one project or the whole site.

Security scanner

See Security scanner.

• Scans the history a report loads, current and historical values, for 55 kinds of secret and personal data in four categories: secrets and credentials, financial and government IDs, personal data, and network addresses.
• Checksums and shape checks where they apply: Luhn for cards, mod-97 for IBANs, ABA for routing numbers, reserved-range checks for US Social Security numbers.
• Each finding marked Current or Historical, with a severity from 1 to 5.
• Filters by minimum severity, category and text.
• Values masked by default, with unmask per row and Unmask all values.
• Remediation guidance for each category.
• CSV export of the findings, masked unless you unmask them first.

Dashboard gadgets

See Dashboard gadgets.

• Work item activity: the latest field changes for chosen projects, with 10 to 100 rows.
• Status over time: a stacked daily (or weekly) chart of work items in each status.
• Configured with a title, projects, extra JQL (checked by Jira’s parser), dates and a search.
• Refresh, auto-refresh every 5, 15 or 60 minutes, and Open the full report into the explorer.
• Each viewer sees the gadget through their own Jira permissions.

Rovo agent: UndoTrail Assistant

See Rovo agent.

• Ask in plain words about change history, deleted work items, or secrets and personal data in the history.
• Understands projects, keys, JQL, fields, transitions, people, periods and search words.
• Answers with counts, the matching changes or items, and a link that opens the same report in UndoTrail.
• Scanner values always masked in answers.
• Follows the same feature permissions and Jira permissions as the app.

Get change history from Jira’s search

• In Jira’s work item search, the app action Get change history opens the explorer with the search’s JQL already filled in.

Administration

See Admin settings.

• Subscription status, and free access codes for pilots and reviewers.
• Retention for deleted work items, 1 to 365 days.
• Comment and viewer tracking switches, and project exclusions.
• Time format for durations: Jira style (1w 2d 3h), decimal hours or minutes, with hours per day and days per week.
• Permissions for six features (history reports, export, revert, deleted items, security scanner, viewer history): everyone, Jira admins only, or named Jira groups. The security scanner starts as Jira admins only. Jira administrators always have access.
• Backfill, erasing tracking data, scheduled reports, verifying a signed export, and a summary of what the app stores.

Security and privacy

See Permissions and security.

• No egress permission: the app cannot send your data outside Atlassian, because Forge blocks any call out.
• Eligible for Runs on Atlassian.
• History read in your browser as you, so Jira’s own permissions decide what anyone sees.
• Restores, reverts and comments written as you, so Jira’s audit trail names the person.
• Eleven Atlassian scopes, each explained.
• Feature permissions checked on the server wherever the app’s backend serves data, and features kept closed if permissions can’t be loaded.
• Only a small amount of data stored, in Forge storage on your own site, in the region Atlassian assigns to it.
• Logs carry operation names, keys and counts, never field values, summaries, descriptions or comment text.
• Atlassian’s weekly personal data report: closed accounts are erased or shown as Former user, and changed names are refreshed, everywhere the app stores them.

Help, guidance and accessibility

• A first-run getting-started guide and a quick tour of the Changes tab, both replayable.
• A Help panel: where everything is, keyboard shortcuts, and What’s new in the current version.
• Full keyboard use: arrow keys between tabs and through a field’s history, focus kept inside dialogs, and Esc to close.
• Screen-reader labels on every control, announced report totals, and diffs read as “removed” and “added”.
• Light and dark themes following Jira, and layouts that work from a narrow dashboard column to full screen.