Matify/Config Undo for Jira

Config Undo for Jira

Change history and verified restore for Jira configuration. See who changed a scheme, workflow or screen and when, and put an earlier version back โ€” previewed, approved and verified.

What it does

  1. Records changes to permission and notification schemes, workflows, workflow schemes, screens, custom-field options, field schemes and project settings, from the hourly audit-log poll, Jira events and a rolling reconcile.
  2. Starts with history: on installation the change journal is filled from your Jira audit log and workflow history.
  3. Compares any two captured versions of an object, or a version with live Jira.
  4. Restore points record the captured state of your configuration before a planned change.
  5. Restores one object to an earlier version: a preview shows the changes, affected projects and limits; a second Jira admin approves by default; the app re-reads Jira and reports whether the result matches.
  6. Ledger: requests, approvals and results are kept in a hash-chained record with an integrity check.

Trust

Restore is off until a Jira admin enables it per configuration type. Config Undo runs on Atlassian Forge, keeps its data in Forge hosted storage on your site and sends nothing outside Atlassian. It stores Atlassian account ids, never people's names. Field schemes are history and compare only; see the known limitations.