Documentation

Install and get started

Requirements: Jira Cloud and a user with the Administer Jira global permission. ConfigRadar is a Forge app that appears under Apps → ConfigRadar in Jira administration.

1. Install. Open ConfigRadar on Atlassian Marketplace and choose Try it free, or find it in the Atlassian Marketplace from inside Jira.
2. Open ConfigRadar from the Apps menu in Jira administration.
3. Wait for the backfill. On install, the app imports the last 30 days of the Jira audit log and takes the first configuration snapshot. Progress is shown in the app.
4. Explore the timeline, open a change to see its diff, and add critical objects to your watchlist.

Only Jira administrators can open ConfigRadar. Every request checks the Administer Jira permission of the signed-in user.

ConfigRadar supports Jira's light and dark themes.

Editions

ConfigRadar comes in two editions, both with a 30-day free trial. Features marked Advanced on this page are only in the Advanced edition, and features marked Coming in Advanced are planned for it.

• Standard: audit log history with hourly sync, daily snapshots, before/after diff, timeline with filters, watchlist with in-app alerts, CSV export and 90-day retention.
• Advanced: everything in Standard, plus alerts as Jira issues, baseline and drift detection and retention up to 3 years. PDF compliance evidence export, a dashboard gadget, a Rovo agent and a scheduled change digest are coming in Advanced.

See Pricing for prices per edition.

Audit log history

ConfigRadar reads the Jira audit log and keeps its own history, so you are not limited by what Jira shows in its audit screen.

• Backfill: 30 days of audit records are imported on install.
• Ongoing: new records are imported every hour. If a run fails, the next run picks up from where the last one stopped.
• Privacy: IP addresses in audit records are discarded and never stored. The author's Atlassian account ID is kept so you can see who made a change.

Snapshots

Once a day ConfigRadar takes a snapshot of the content of these configuration objects and stores it in Forge SQL:

• Workflows and workflow schemes
• Custom fields and their contexts
• Screens
• Permission schemes
• Project settings

Only objects that changed get a new version, so history stays compact.

Before/after diff

The Jira audit log often says only that an object was updated. ConfigRadar compares two versions of the object and shows a before/after diff: added or removed transitions and statuses, changed field contexts and options, screen tabs and fields, permission grants and project settings.

Timeline and filters

The timeline merges audit log entries and snapshot diffs into a single list of changes. Filter by object type, project, author and date range, and open any entry to see its diff.

Watchlist and alerts

Add workflows, schemes, fields or projects to the watchlist. When a watched object changes, ConfigRadar raises an alert:

• In the app, in the Alerts view.
• As a Jira issue in a project and issue type you choose Advanced. Jira sends its usual notifications for that issue according to the project's notification scheme, so no email leaves the app.

Creating alert issues (Advanced) is the only thing ConfigRadar writes to Jira. You can turn it off and keep in-app alerts only.

Baseline and drift Advanced

Save a snapshot as a baseline, for example after a release or an approved configuration review. ConfigRadar then shows drift: every object that differs from the baseline, with its diff.

Exports

Export changes from a date range as CSV for audits, change reviews and spreadsheets. Advanced will also let you export a PDF compliance evidence report of changes for a period Coming in Advanced.

Exports are generated inside Forge and downloaded by the signed-in admin. They are not sent to Radrly.

Dashboard gadget Coming in Advanced

The ConfigRadar gadget will let you see recent configuration changes and open alerts at a glance on a Jira dashboard.

Rovo agent Coming in Advanced

You will be able to ask the ConfigRadar agent in Rovo chat, for example “what changed in project X this week?”, and get an answer from ConfigRadar's change history with links. The agent will run inside Atlassian and require Rovo on your Jira site.

Change digest Coming in Advanced

A scheduled summary will be available of configuration changes for a period, delivered inside Atlassian. No email or webhook leaves the app.

Retention

ConfigRadar keeps change history for 90 days in Standard and up to 3 years in Advanced (set in Settings). A daily job deletes older records, except current versions and versions used by a baseline.

Data and residency

ConfigRadar stores its data in Atlassian Forge hosted storage (Forge SQL and Key-Value Store). It makes no calls outside Atlassian. The data follows your Jira site's data residency location.

Data stored by the app:

• Audit log entries (without IP addresses)
• Configuration snapshots and diffs
• Atlassian account IDs of change authors and of admins who acknowledge alerts
• Watchlist, baselines, alerts and app settings

Display names are not stored; they are looked up from Jira when a page is shown. ConfigRadar does not store issue content, comments or attachments, and audit records about user management are skipped.

FAQ