- Overview
- Getting started
- User guide
- Restore guide
- Permissions and security
- Privacy and data
- Large sites
- Troubleshooting
- FAQ
- Known limitations
- Changelog
Config Undo for Jira — Documentation
Config Undo for Jira records changes to your Jira configuration and lets a Jira administrator put an object back to an earlier version: previewed, approved and verified. It is published by Matify and runs on Atlassian Forge inside your Jira Cloud site.
What it covers
| Configuration type | Recorded and compared | Restorable |
|---|---|---|
| Permission schemes | Yes | Yes |
| Notification schemes | Yes | Yes |
| Workflows | Yes | Yes |
| Workflow schemes | Yes | Yes, when no issue needs to move to another status |
| Screens (tabs, fields, field order) | Yes | Yes |
| Field options (per custom field context) | Yes | Yes |
| Project settings (details, scheme associations, role actors, components, versions) | Yes | Yes, with exceptions listed in Known limitations |
| Field schemes | Yes (experimental Jira API) | No, history and compare only |
Company-managed projects only. Team-managed projects, issue security schemes, boards, filters, dashboards, automation rules and issue data are not covered.
Pages in this documentation
- Getting started: install, the first hour, the guided safe test, your first restore point, turning restore on, approvals
- User guide: concepts (configuration types, versions, journal sources, restore points, ledger) and every page of the app
- Restore guide: preview, warnings, blocked cases, approval modes, verification results, undoing a restore, the restore incident playbook
- Permissions and security: the six scopes in plain words, what the app user can do, how restores appear in Jira's audit log
- Privacy and data: what is stored, where, for how long, and how to delete it
- Large sites: onboarding time and Jira's rate limits
- Troubleshooting: every error code and what to do
- FAQ
- Known limitations
- Changelog
Requirements
- Jira Cloud. Config Undo is installed into Jira and works with company-managed projects of every Jira-family product on the site.
- Only users with the Administer Jira global permission can open the app. Everyone else sees "You need Jira administrator permission to use Config Undo."
- The history Config Undo can backfill depends on what your site's Jira audit log still holds (audit retention depends on your Jira plan). If Jira doesn't let the app read the audit log at all (for example on Jira Free), Config Undo still records changes through Jira events and the daily reconcile, but without the author and without history from before the installation. Coverage & Health says so.
Installation
- Open the Config Undo for Jira listing on the Atlassian Marketplace (or search for it from Settings (gear) → Apps in Jira) and start the free trial (30 days; sites with up to 10 users are free). Installing needs a Jira site administrator.
- Review the permissions Jira asks you to approve. They are explained in Permissions and security.
- After installation open Settings → Apps → Config Undo. Its pages appear in Jira's admin sidebar: Journal, Objects & Compare, Restore points, Restores, Ledger, Coverage & Health, Settings.
Recording starts by itself about two minutes after installation. Restore stays off until you turn it on.
Licensing and trial
- 30-day free trial with the full product (a banner shows when the trial ends); free for sites with up to 10 users.
- While the licence is inactive, Config Undo is read-only. The journal, versions, compare (which then records no new versions), the ledger and exports stay available, and "Delete all app data" still works. 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. Recording resumes by itself once the licence is active again; the next hourly poll catches up on the audit log.
Uninstalling
Before uninstalling, export what you want to keep (journal CSV, ledger CSV/JSON, single versions as JSON). On uninstall, Config Undo writes a final UNINSTALL entry to its ledger. Its stored data stays in Atlassian's Forge hosted storage and is retained and deleted per Atlassian's Forge data retention for uninstalled apps; nothing is sent to Matify. To remove everything first, use Settings → Danger zone → Delete all app data. Details: Privacy and data.
Support
Email support@matifyapps.de, use the login-free form or the public tracker linked from the support page. Include the diagnostics file from Coverage & Health → Download diagnostics; it contains no account ids, names or configuration content. Response times are in the Matify service level agreement.
Security issues: never in a public ticket. Email support@matifyapps.de with "security" in the subject.
More: Data security and privacy statement · Privacy policy · Terms