Matify/Config Undo for Jira

FAQ

Is Config Undo a backup of my Jira data? No. It records and restores configuration: permission and notification schemes, workflows, workflow schemes, screens, field options and project settings (plus field-scheme history). It doesn't back up or restore issues, comments or attachments.

Does it change anything in Jira after installation? No. Recording only reads. Restore is off for every type until a Jira admin turns it on, and even then each restore needs a preview, a reason and an approval. The only write you can trigger without that is the guided safe test, which uses a test permission scheme the app creates and then deletes; the kill switch and the licence apply to it as well.

Why does the app need Jira-admin-level permissions? Reading the audit log, workflows and notification schemes needs manage:jira-configuration, and putting configuration back needs it and manage:jira-project. Jira gives an app with these scopes Jira-admin-equivalent rights. See Permissions and security for what the app does with them and the safeguards.

Who can use it? Users with the Administer Jira global permission. Restores need a second Jira admin to approve by default.

We have only one Jira admin. Can we still restore? Yes. Switch Settings → Approval to Single admin; you approve your own request by typing the object's exact name. The guided safe test works on single-admin sites without that switch.

How far back does the history go on day one? As far as your Jira audit log still goes, up to 180 days during onboarding, plus 60 days of workflow history. After onboarding, Coverage & Health → Import older history can import older audit records if Jira still has them (entries older than your retention period are removed again). Audit-log entries show what the audit log recorded; only complete versions can be restored. Once Config Undo has captured an object, every later change to it is stored as a complete version; on busy sites the first capture of some types follows in the hours after installation, so a change made before that can't be undone. If Jira doesn't let the app read the audit log (for example on Jira Free), there is no history from before the installation.

How quickly does a change show up? Within about an hour (hourly audit-log poll); changes to projects, versions, components, fields and field contexts often within minutes. Compare with live captures an object listed in Objects & Compare immediately. Changes Jira doesn't audit are found by the weekly (on large sites four-weekly) reconcile.

What does "verified" mean? After writing, Config Undo reads the object back from Jira and compares it with the version you chose. PASS means they match. PASS_WITH_NOTES means they match except items kept on purpose (disabled options, archived versions, components to remove manually) or recreated with new IDs.

Can I undo a restore? Yes. Before every restore the live state is saved as a version ("Before restore"). Restore that version like any other.

Can I restore a whole restore point at once? Not in this version. Open the restore point, turn on "Only objects changed since the restore point", and restore objects one by one; each has its own preview and approval.

Can it restore a deleted scheme or workflow? A deleted permission scheme or workflow can be recreated as a new object with a new ID (not associated with projects). Deleted notification schemes, screens and workflow schemes are not recreated in this version; download the version as JSON and recreate it in Jira.

Why was my workflow scheme restore blocked? Because it would require moving issues to other statuses. Config Undo doesn't perform status migrations. Apply that change in Jira's workflow scheme editor.

Does any data leave Atlassian? No. Everything is stored in Forge hosted storage on your site and follows its data residency. The app has no external connections, no analytics and no subprocessors besides Atlassian.

Does it store personal data? Atlassian account ids (in configuration and in the app's own records), free text admins type (reasons, notes), and email addresses only where an admin configured them as notification recipients. No names of people. Details: Privacy and data.

How long is data kept? 13 months by default (3–36 months in Settings). The latest version of each object, the version that was live at the retention boundary and pinned restore points are always kept, so a change to a long-unchanged object can still be undone. Finished restore requests and unpinned restore points are removed once older than the retention period; previews nobody submitted after 24 hours. The ledger is kept for the life of the installation. Details: Privacy and data.

Does it cover Jira Service Management and Jira Software projects? Config Undo records and restores the Jira configuration that company-managed projects use: schemes, workflows, screens, field options and project settings. It has no features specific to Jira Service Management, such as request types, queues or SLAs. Team-managed projects are not covered.

What happens when the licence expires? Config Undo becomes read-only: the journal, versions, compare (without recording new versions), existing restore points, the ledger and exports stay available. Restores, previews, new restore points, reviews, settings changes and the guided test are blocked, and background recording pauses. Recording resumes by itself and catches up once the licence is active again.

What does the kill switch do to a restore that is already running? It stops it before its next write step. What was already written is verified, not rolled back, and the request shows Restored with differences; after turning the kill switch off you can retry the remaining steps within one hour.

How does it handle large sites? It spreads the first capture over hours, and over several days on very large sites, to stay within Jira's rate limits. Approved restores are never blocked by these budgets. Comparisons with live Jira, previews and restore points share an hourly cap per site. See Large sites.

Is Config Undo certified (SOC 2, ISO 27001)? No. Config Undo runs entirely on Atlassian's Forge platform; Matify holds no certification and claims none.

Where do I get help? support@matifyapps.de, the login-free support form or the public tracker on the support page. Include the diagnostics file from Coverage & Health.