Astrospray
scroll

Every change in your Jira audited. And the power to put it back.

Jira records every change to every work item. It just can't read them back to you. UndoTrail shows you every change anyone has ever made, across every project, then puts it back in a couple of clicks. Even the work items somebody deleted.

Ask us about UndoTrail Read the docs
Who changed the priority on these forty items? Filter by person, field, sprint or date. No JQL.
Was that us, or the automation rule? Automation and bulk edits carry a BULK marker
Can I see it ticket by ticket? Every change grouped under its work item
What was it before? Both sides of every field, custom ones included
Can the auditor have it by Friday? Excel, CSV or PDF, signed, up to 150,000 changes
Jira says: Recorded · one item at a time
UndoTrail answers: 0 questions

From: Head of Delivery · Mon 09:05 Subject: Quick question about Jira

Jira recorded the answer. Now go and find it.

Five questions this morning, and the honest answer to each is "I'll look into it."

To: Head of Delivery · Mon 09:07 Subject: Re: Quick question about Jira

All five answered. Before the meeting.

Every change, every project, on one screen. And if one was a mistake, one click puts it back.

For years you've been told Jira has an audit trail. It does. You just can't read it. Jira hands you a perfect record one work item at a time, and the day someone asks a real question, a perfect record turns into a very long afternoon.

Take the three-question test

Be the one with the answer

You want to never again say four words in a meeting: "I'll look into it." They cost you an afternoon, sometimes a week, and a little credibility every time.

What you want is a different Monday morning. The question gets asked, and you answer it in the meeting it was asked in.

Four colleagues smiling round a laptop while one points at the answer on screen

The questions that arrive with a senior name attached

  • "Who changed the priority on these forty items last quarter?" That's forty tabs.
  • "Which of these were us, and which were that automation rule?" That's a guess.
  • "The client escalation ticket has gone. Can we get it back?" When a work item is deleted, its history goes with it.

Jira is superb at recording work. It was never built to answer questions about the record. But you're the one they ask.

PAY-1042 · History1 of 40
  • Priya Shah changed the Priority · 3 days ago
  • Tom Reid changed the Status · 9 days ago
  • Automation for Jira changed the Labels
UndoTrail filtered to bulk changes: every automation edit marked BULK, all selected, ready to revert

The three-question test

Could you answer these before your coffee goes cold?

Try them on your own Jira. All three inside five minutes? Stop reading: you're already the one who knows. If not, the rest of this page is about closing that gap.

Every change, as one list

Every change to Status, Assignee and Priority, across all your projects, in the last 30 days, with who made each one.

Start the stopwatch

People, or robots?

Of last week’s changes, which were people and which were an automation rule or a bulk edit?

Still running

The epic, deleted

If your most important epic were deleted in the next hour, with its subtasks, what could you restore? Which fields? In what status?

The one that matters most

Where the answers live today

Three places to look. One long afternoon.

Each of these is good at the job it was built for. Watch what each one tells you about the same forty priority changes.

PAY-1042 · History1 of 40
WhoFieldFromToWhen
Priya ShahPriorityHighLow3 days ago
Priya ShahAssigneeTom ReidPriya Shah5 days ago
Tom ReidStatusTo DoIn Progress9 days ago
Item 1 of 40. Open the next tab.
Search results · export.csv40 items
KeySummaryPriorityUpdated
PAY-1042EU card payments failingLow3 days ago
PAY-1038Refund webhook retriesLow3 days ago
PAY-10313DS challenge timeoutLow3 days ago
PAY-1027Settlement report driftLow3 days ago
Shows "Low". Not who made it Low, or what it was before.
#deliveryMonday 09:07

Head of Delivery
Who dropped the priority on the PAY escalations? The client is asking.

You
I'll look into it.

Answer due: this afternoon, probably.
UndoTrail · Priority changes, last 30 daysAll projects
WhenWhoItemFromTo
19 Sep 02:14Automation BULKPAY-1042HighLow
19 Sep 02:14Automation BULKPAY-1038HighLow
19 Sep 02:14Automation BULKPAY-1031MediumLow
18 Sep 16:40Priya ShahPAY-1027HighLow
40 changes, one screen. 39 were the 02:14 rule.

What UndoTrail answers

Eight questions Jira records the answer to, and never shows you.

Every change, on every work item, across every project. Nothing to switch on, and the app never sends your data outside Atlassian.

Who changed this?

Who, what, from what, to what, and when, across every project on one screen. Filter without JQL, or on a transition like In Progress to Done.

Put it back

Undo one change or ten thousand. A dry run first, and a check that never overwrites a colleague’s later edit.

Deleted, then restored

Deleted items land in a bin with who and when, and come back whole: custom fields, subtasks, comments and status.

One file for the auditor

Excel, CSV or PDF, up to 150,000 changes in one report, signed with a SHA-256 hash so anyone can prove it is untouched.

Secrets still in history

55 detectors for keys, tokens, card numbers and personal data, across current and historical values.

What the comment said then

Jira keeps no record of an edited comment’s old text. UndoTrail keeps every version, with who changed it and when.

Who opened it

"I never saw that ticket." Check instead of asking round the office. Viewer history records from install.

How long it sat there

Time in each status, added up. Take a number to the retro instead of a hunch, as far back as Jira’s record goes.

When an automation rule rewrites six hundred work items at 2am, Jira has no undo button. We built one.

See it put back

Undo the bad night

One change or ten thousand, put back before lunch.

See exactly what will be written, then press go. Nothing is written without a preview.

Dry run Nothing written yet
Revert · dry runRule: "Tidy priorities"
ItemFieldNowGoes back to
PAY-1042PriorityLowHigh
PAY-1038PriorityLowHigh
PAY-1031PriorityLowMedium
OPS-311PriorityLowHighest
… and 596 more
Revert · writingRe-read at write time
ItemFieldResult
PAY-1042PriorityWritten
PAY-1038PrioritySkipped: Tom Reid changed it at 08:12
PAY-1031PriorityWritten
OPS-311PrioritySkipped: Priya Shah changed it at 08:40
Nobody's later edit was overwritten.
Revert · complete22 Sep 2026, 09:31
OutcomeItems
Written598
Skipped, edited since2
Failed0
revert-2026-09-22.csv · ready to download
Ready to revert 600 / 600

Every change the rule made, and exactly what each field will go back to. You read it first, then you press go.

Get back what someone deleted

It comes back In Progress, not To Do.

Capture is on from the minute you install. Nothing to switch on, no webhook to configure.

  • Know who deleted it and when. Deleted items land in a bin with both.
  • Restore it whole: custom fields, subtasks, comments, and its status.
  • Preview first. See field by field what you're getting back, and edit the summary, labels or target project before you commit.
  • Nothing happens until you say so.

Drag to restore

PAY-1042 · Deleted by Sam Hale, 22 Sep 16:42

Client escalation: EU card payments failing at checkout

Status
unknown
Subtasks
unknown
Comments
unknown
Customer tier
unknown

PAY-1042 · Restored by you, 22 Sep 16:45

Client escalation: EU card payments failing at checkout

Status
In Progress
Subtasks
3 of 3, with their own status
Comments
12, every version
Customer tier
Enterprise
In the bin Restored
Custom fields ✓ Subtasks ✓ Comments ✓ Status ✓

Hand the auditor one file

Built for the size real audits are, not the size demos are.

Screenshot: report filters

Step 1 · Build

The report, in plain filters

Person, field, sprint, saved filter or date range. Everything except this person is one click.

Screenshot: colour-coded export

Step 2 · Export

Excel, CSV or PDF

Colour-coded before and after, every timestamp in UTC and local time, up to 150,000 changes in one file.

Screenshot: signing record

Step 3 · Sign

Proof it has not been touched

A SHA-256 hash, recorded with who signed it, why and when. Plus a settings sheet saying how it was built.

Screenshot: scheduled report

Step 4 · Schedule

Every month, without asking

The report arrives as an attachment on a work item you choose. The auditor stops having to ask.

Runs on Atlassian

Your security team's first question, already answered.

"Does it send our data anywhere?" No, and it can’t. UndoTrail runs entirely on Atlassian’s own infrastructure, with no permission to send data outside it. Atlassian’s platform enforces that on every deployment: a technical fact, not a policy promise.

0 Bytes of your data the app sends outside Atlassian No outside connections at all
8 Atlassian scopes requested Each justified in the security statement
1,116 Automated tests on every change Including every way an export has failed
250,000 Rows in one tested export Time zones, giant fields, duplicate columns
  • Nobody sees more than Jira already shows them. Every report runs as the person who asked.
  • Nothing is written without a preview. Revert shows a dry run; restore shows field by field.
  • Admins decide who gets what. Reports, exports, revert, restore and the security scanner: each open to everyone, kept to Jira admins, or given to chosen groups.
  • Nothing for you to host or patch. It lives inside Atlassian’s own cloud.
Read the security statement

Answers without leaving Jira

One screen. Every change.

A History+ tab inside every work item, dashboard gadgets, share links that open the identical report, and a Rovo agent you can simply ask: “What changed on the PAY project yesterday?”

Recording of the live product to come

A recording of the report explorer goes here.

Covered three minutes from now

Install it. Run one report. Press one button.

That's it. The next time someone asks what happened, you'll have the answer. And if it needs putting right, you can put it right.

Install it

From the Atlassian Marketplace. Capture is already on the moment it lands.

About a minute

Run your first report

Pick a project, press Run. Every change, who made it, what it was before.

One click

Snapshot everything

Press "Snapshot every work item" once, so even items nobody has touched since install are fully restorable.

Once, then never again

One plan. Everything in it.

You can't choose your bad day. So why choose a plan?

Free for up to 10 users. One published price above that, with every feature in it.

Bulk revert, the security scanner, the advanced reports: every one is a bad-day feature, and the bad day is exactly when you can't stop to upgrade. So the day you install is the day you're covered for all of it.

UsersPer yearPer day
Up to 10FreeFree
50$525about $1.44
100$1,050about $2.88
500$3,185about $8.73
1,000$4,935about $13.52
  • One plan, everything included. Nothing you need later is behind a higher price.
  • One published price. Nobody negotiates a better deal than you get.
  • If your subscription lapses, capture keeps running and nothing stored is deleted.
  • A feature in the plan today stays in the plan.
  • Billing runs through Atlassian, and a refund within their policy is never contested.
  • A person answers. Target for a first reply: four business hours.

Do one sum with your own numbers: the day rate of whoever assembles your audit evidence, times the days it took last time. For most teams, UndoTrail costs less for the whole year than that one afternoon.

Restoring a work item needs a snapshot taken before it was deleted, and snapshots start the minute UndoTrail is installed. It's insurance, and like all insurance, it's bought before the accident.

Ask us about UndoTrail

Questions

The questions people ask first.

No, and it can’t. It runs entirely on Atlassian’s own infrastructure and has no permission to send data outside Atlassian. The platform enforces that on every deployment.

Every report runs as the person who asked. If Jira wouldn’t show them a project, UndoTrail won’t either. Not one row more.

Install it and capture is on. There is no webhook to configure and nothing to host. Press "Snapshot every work item" once, and everything is restorable from that moment.

Yes. Every feature has its own switch. Reports, exports, revert, restore, the security scanner and viewer history can each be open to everyone, kept to Jira admins, or given to the Jira groups you choose. The scanner starts with admins only. Comment and viewer history can be switched off, or left out of projects such as HR or Legal.

Capture keeps running and nothing stored is deleted. Each work item’s own history stays free for ever, so a lapse never leaves a hole in your audit trail.

Free for up to 10 users, and one published price above that with every feature included. The table above has the common sizes.

A person who knows the product. Email help@astrospray.com; our target for a first reply is four business hours.

P.S. Go back to question three. If your honest answer was "nothing", that's the one to fix first, because it's the only one that gets worse every day you leave it.

Not ready yet? Forward this page to your security team with one line: "No egress, eleven scopes, runs as the user."

Ask us about UndoTrail

More from Astrospray

UndoTrail documentation Read the docs Security statement Read it Atlassian Jira apps See them all OpenCart extensions Find out more