Matify/Config Undo for Jira

User guide

Concepts

Configuration types ("families")

Config Undo works with eight types of Jira configuration. Each object has a stable key (for example PS:10000 for permission scheme 10000), shown on its page in Objects & Compare.

TypeWhat a version containsHow changes are detectedRestore
Permission schemename, description, every grant (permission + holder)audit logyes
Notification schemename, description, recipients per eventaudit logyes
Workflowstatuses, transitions, conditions, validators, post functions, descriptionaudit log; workflow history during onboardingyes
Workflow schemedefault workflow and issue type → workflow mappingsaudit logyes, if no issue would need a status migration
Screentabs, fields per tab, field order, name, descriptionaudit logyes
Field optionsoptions of one custom field context: value, enabled/disabled, order (select, multi-select, radio, checkboxes, cascading select)audit log (Jira sends no event for option edits)yes
Project settingsname, description, lead, default assignee, category, scheme associations, role actors, components, versionsaudit log and Jira project/version/component eventsyes, with exceptions
Field schemefield scheme parameters (experimental Jira API)reconcile onlyno, history and compare only

Coverage & Health shows the detection mode per type.

Versions

A version is a complete, normalised copy of one object at one point in time. Config Undo stores a new version only when the content changed (the content is hashed; identical content is stored once). Each version has a source:

SourceMeaning
Baselinefirst capture during onboarding
Audit logcaptured after the hourly audit-log poll saw a change
Jira eventcaptured after a Jira product event (projects, versions, components, fields, field contexts)
Reconcilethe rolling reconcile found a change that had no audit record or event; the author is unknown
Backfill (audit log)history taken from the audit log during onboarding or by Import older history: shows what the audit log recorded, not a complete version, can't be restored
Backfill (workflow history)a complete earlier workflow version from Jira's workflow history (up to 60 days)
Restorethe state after a restore by Config Undo
Before restorethe live state saved right before a restore wrote anything ("rollback of the rollback")
Restore point re-readcaptured by "Re-read everything now" on a restore point
Manual re-readcaptured by "Compare with live", a preview or the guided test

The change journal and its sources

The journal is one timeline of changes: who changed which object, when, and what changed. Changes come from:

Authors come from the audit log and are stored as Atlassian account ids; names are looked up when you view a page. When Jira's audit record names no author (for example automatic changes Jira makes itself), the author column shows Not recorded by Jira. Changes found by reconcile say "detected by reconcile, author unknown". Some entries carry a High impact marker: a grant removed from Browse projects or Administer projects, a status removed from a workflow, or any change to an object used by more than ten projects.

Restore points

A restore point is a named list of "the version of every object that was current at this moment", for all or some configuration types. When only a few changes are waiting since the last hourly poll (up to 15 objects), creating one captures them first; it then records the list and a freshness time per type. Restore points are created by hand or automatically once a week. Restore points older than the retention period are removed by the weekly maintenance run unless they are pinned; pinned restore points, and the versions they reference, are kept regardless of retention.

Restore requests

A restore request puts one object back to one version. It goes Preview → Request → Approve → Result, and every step is recorded. See the Restore guide.

The ledger

The ledger is an append-only record of every restore request, approval, rejection, expiry, execution, verification result, settings change, data deletion and uninstall. Each entry carries a hash over its core fields (sequence number, time, type, request, object, before and after hash, verification result and the person's token) and the hash of the previous entry. Changing or removing an entry's core fields, or removing an entry, breaks the chain, and the integrity check finds it. People are referenced in the hashed part by a random token, not by their account id, so erasing a closed account keeps the chain verifiable. The entry's short text summary and the plain account id are stored next to the hashed part, so the check does not cover them.

Pages

Journal

Objects & Compare

Restore points

Restores

Tabs: Pending approval, In progress, History. A request shows its preview and write plan, reason, requester, approver, a timeline with ledger entry numbers and the verification result. Actions depend on the state: approve, reject (with an optional note), cancel, retry remaining steps, preview again.

Ledger

Entries newest first, with sequence number, time, type, request, object, before and after hash, verification result, actor, entry hash and previous hash. Verify integrity recomputes the chain and reports the first entry that doesn't verify, if any. A long ledger can't be checked within one request: the page then says how many entries verified so far, and the whole chain is then checked again in a background job, with the result shown in Coverage & Health. The chain head (latest entry number and hash) is shown so you can record it outside Jira. Export as CSV or JSON.

Coverage & Health

Settings

SettingDefaultRange / notes
Disable all restores (kill switch)offBlocks every write to Jira: no restore can be submitted, approved or retried, and the guided safe test can't start, restore or clean up. A running restore stops before its next write step; what it already wrote is verified and the request ends as Restored with differences (it is not rolled back). Recording and compare keep working.
Allow restores of … (one switch per restorable type)all offTurning one on shows what may change and is recorded in the ledger
Approval modeFour-eyesSingle admin: the requester approves by typing the object name
Approval expires after (hours)24 hours1–72 hours; unapproved requests expire and change nothing
Keep versions and journal entries for (months)13 months3–36 months; reducing it needs a confirmation and shows an approximate count of the stored versions older than the new period (some of them are kept anyway; see Privacy and data)
Create an automatic restore point every weekon, Monday (UTC)any weekday (Weekday (UTC)); created once onboarding has finished
Exclusionsnoneobjects (by key) or projects that are not recorded; existing history ages out with retention like any other, and each object's latest version is kept
Reconcile cadenceAutomatic, based on site sizeWeekly or Monthly
Record field schemesonexperimental Jira API; history and compare only
Delete all app data—type DELETE ALL CONFIG UNDO DATA

Every settings change is recorded in the ledger. While the licence is inactive, settings are read-only (exports and Delete all app data still work).

Exports

ExportWhereFormatContents
JournalJournal → Export CSV / Export JSONCSV, JSONthe current filter: time (UTC), type, object, change, author, source, summary, review status, reviewer, note
Review reportJournal → Review report (CSV)CSVthe journal rows of the current filter with review status, reviewer and note, as change evidence
LedgerLedgerCSV, JSONevery entry with sequence, type, request, object, actor token and account id, before/after hash, verification result, previous and entry hash; the export also records the chain head
One versionobject pageJSONthe normalised object, for manual re-entry or an offline archive

CSV files are UTF-8 with a byte-order mark. Every cell that starts with =, +, -, @, a tab or a carriage return is prefixed with ', so spreadsheet programs don't run it as a formula. Display names are added to journal and review exports when you export; the ledger is exported exactly as stored.

Licensing

Trial and active licences: everything is available; during a trial a banner shows when it ends. Inactive licence: read-only. The journal, versions, compare (without recording new versions), existing restore points, the ledger, exports and Delete all app data stay available. Restores, previews, creating or re-reading restore points, journal reviews, settings changes, Import older history and the guided safe test are blocked, and background recording pauses. After the licence is active again, recording resumes by itself and the next hourly poll catches up on the audit log since the last poll.