- Overview
- Getting started
- User guide
- Restore guide
- Permissions and security
- Privacy and data
- Large sites
- Troubleshooting
- FAQ
- Known limitations
- Changelog
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
- Team-managed projects and their workflows and schemes. Only company-managed configuration is recorded and restored.
- Issue security schemes, boards, filters, dashboards, automation rules, screen schemes, issue type schemes and issue type screen schemes as objects. (The association of a project with an issue type scheme or issue type screen scheme is part of project settings and is restored.)
- Issue data: issues, comments, attachments, deleted issues. Config Undo is not a backup of issue data and doesn't revert bulk issue changes.
- Jira Service Management specifics: request types, queues, portal settings, SLAs.
- Global settings, users, groups and licences. Apps can't create groups, so a grant to a deleted group is skipped.
- Moving configuration between sites or from a sandbox to production.
- Restoring deleted custom fields or projects: use Jira's own trash, then Config Undo can restore their settings or options.
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
- Options, components and versions deleted since the chosen version are recreated with new IDs. Issue values that pointed at the deleted ones are not restored.
- Statuses deleted from the site are recreated with new IDs; issues that were in them are not moved back.
- A deleted permission scheme or workflow is recreated as a new object with a new ID. It isn't associated with any project or workflow scheme; associate it again in Jira, or restore the projects' settings.
- Removed permission grants are added again; Jira gives them new IDs (harmless).
Nothing is deleted that might hold data
- Options added since the chosen version are disabled, not deleted.
- Versions added since are archived, not deleted.
- Components added since are listed for manual removal with their issue counts, never deleted.
- Screen tabs added since are emptied and deleted, as the write plan lists.
Workflows and workflow schemes
- A workflow scheme is restored only when Jira reports that no issue would need to move to another status. Anything that needs a status migration is blocked with an explanation; export the version and apply it in Jira's workflow scheme editor.
- Removing a status from a workflow that projects use through an active workflow scheme is blocked.
- Jira's workflow API can't rename workflows; a name difference is listed for manual action.
- Status definitions (name, category) are shared by all workflows; a site-wide rename or recategorisation is not undone.
- Every workflow restore must pass Jira's own validation, including third-party rule configuration; a validation error blocks it.
- Read-only system workflows can't be changed.
- Deleted workflow schemes are not recreated in this version.
Project settings
- Restored: name, description, lead, default assignee, category, permission / notification / issue type screen / issue type scheme associations, project role actors, components and versions.
- Journal and manual guidance only: project key, project type, workflow-scheme association (switching migrates issues; do it in Jira's project settings) and issue-security-scheme association.
- Jira can't set a project back to "no notification scheme"; the current association is kept.
- Archived projects must be unarchived first; deleted projects restored from Jira's trash first.
- Changing an issue type scheme association fails if issues use issue types the target scheme removes; Jira then changes nothing and the result is FAILED.
Other restore limits
- One object per request. A restore point is restored object by object; there is no batch restore.
- The kill switch stops a running restore before its next write step; it does not roll back what was already written. The request ends as Restored with differences, and you can retry the remaining steps within one hour.
- Deleted notification schemes and screens are not recreated in this version (Jira's create API for notification schemes is experimental). Download the version as JSON and recreate it in Jira.
- Restoring a notification scheme's or screen's name and description uses an experimental Jira API.
- Custom field and context names are not restored; options of fields managed by a Connect app are history and compare only. Context default values are not restored.
- For permission schemes, the list of affected projects is checked for the first 100 company-managed projects; the preview says so when there are more.
- Versions that come from the audit-log backfill hold no complete previous state and can't be restored.
Detection and history
- New changes are picked up by the hourly audit-log poll (or within minutes for project, version, component, field and field-context events). Use Compare with live to capture an object listed in Objects & Compare immediately.
- First hour on busy sites: all background work shares 6,000 estimated points in the first hour after installation. On a site with thousands of audit records that may not cover the whole 30 days of audit history or the first versions of permission schemes, workflows and workflow schemes; they follow in the next hours. A change to an object made before Config Undo captured it can't be undone: its journal entry comes from the audit log and has no complete earlier version.
- Changes Jira doesn't write to its audit log are found by the rolling reconcile: within a week on small and medium sites, within four weeks on large sites. Their author is unknown.
- Jira sends no event for option edits; they are found through the audit log.
- History on day one reaches back as far as your site's audit log still goes (up to 180 days during onboarding) and 60 days of workflow history. After onboarding, Import older history in Coverage & Health imports older audit records as far as Jira still keeps them; imported entries older than your retention period are removed again by the next weekly maintenance run.
- Audit-log retention depends on your Jira plan and settings. If Jira doesn't let the app read the audit log at all (for example on Jira Free), there is no history from before the installation, and recorded changes have no author.
- When Jira's audit record names no author, the journal shows Not recorded by Jira.
Retention
- Versions older than the retention period (13 months by default) are removed weekly. Each object keeps its latest version and the version that was live at the retention boundary, so a change to an object that stayed unchanged for longer than the retention period can still be undone.
- Restore points older than the retention period are removed unless they are pinned, and so are finished restore requests with their preview and result. Pin a restore point if you need it longer.
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.