Matify/Config Undo for Jira

Known limitations

What Config Undo does not do, or does only partly, and why. Most limits come from what Jira's public REST APIs allow an app to do. The restore preview shows the ones that apply before anything is written.

Not covered at all

Field schemes

Field schemes are read through an experimental Jira API. Config Undo records and compares them, but can't restore them in this version. They are detected by the rolling reconcile only (no audit-based detection), so a change shows up within a week (four weeks on large sites). You can turn recording off in Settings.

Restores that create new IDs

Nothing is deleted that might hold data

Workflows and workflow schemes

Project settings

Other restore limits

Detection and history

Retention

Large sites and rate limits

Jira limits how many API calls an app may make per hour, shared across all sites using the app. Config Undo's onboarding therefore takes hours on medium sites and several days on large sites; history for the most important types comes first. Comparisons with live Jira, previews, restore points and the guided test share an hourly cap per site; when it is used up, they are refused with the time when you can try again. Approved restores are never blocked by these budgets. See Large sites.

Audit-log attribution

Restores that run directly appear in Jira's audit log under the approving admin. Longer restores, and the rest of a restore that couldn't finish within the approval request, run in the background and appear under the Config Undo app; the app's ledger records who approved them and when a restore switched to the background.

Interface

English only. Dates and times are shown in your local format and time zone.