Cookies on this site

We use Google Analytics and Ads cookies only with your OK. Privacy policy The ConfigRadar app is not affected and still sends no data outside Atlassian.

Privacy policyChange it any time in Cookie settings at the bottom of the page.

Radrly
ConfigRadar
Try it free

What is ConfigRadar?

ConfigRadar by Radrly is a Jira Cloud app (Atlassian Forge) for configuration change audit: it tracks Jira configuration changes to custom fields, workflows, schemes and permissions, with change history, before and after diffs, and drift against a baseline.

30-day free trial. Standard is free for up to 10 users. Runs on Atlassian, zero egress.

ConfigRadar for Jira: Every config change at a glance. Changes and high-severity events of the last 7 days, the weekly digest and snapshot status for your whole Jira configuration.
  • 211 changes in 7 days
  • 129 high severity
Changes and high-severity events of the last 7 days, in ConfigRadar.

What it does

ConfigRadar is a configuration change audit for Jira Cloud. It gives you a Jira custom field audit log, and the same record for workflows, schemes and permissions, so you can see who changed what, when, and the exact before and after.

  • One timeline of Jira configuration changes. ConfigRadar imports the Jira audit log on a schedule, listens to live configuration events and takes daily normalised snapshots of 22 object types (after a site administrator accepts version 2.0.0; until then, existing installs stay on 1.4.0), including workflows, schemes, fields, field configurations, screens, permission schemes, space roles, groups, statuses, spaces, work types and global settings. After a site administrator accepts version 2.0.0, snapshots also include notification schemes, work item security schemes, field configuration schemes, resolutions, priorities, and, when Jira Service Management is on the site, service projects, request types and queues (22 object types in total). Until then, existing installs stay on 1.4.0. Filter the timeline by object type, change, severity, source and date. Save up to 20 personal timeline views that only you can see.
  • Change history and readable diffs. Open any change to see the before and after, with permission grants shown by name. For an updated workflow, a transitions table lists statuses and transitions that were added, removed, renamed or changed. When a change has more than 5,000 differences, the UI shows the first 5,000 and offers a download of the full versions as JSON. Normalisation means reorder-only noise does not create false changes. Every change can carry an impact explanation and step-by-step revert guidance. ConfigRadar never reverts anything itself.
  • Weekly digest and evidence. Both editions include a weekly digest in the app (the last 7 days by severity and object type, with the top changes), a dashboard gadget for Jira administrators, and CSV export for change-management evidence, including SOC 2 and ISO 27001, with a SHA-256 digest of the file. The in-app UI follows the Jira user's language in 12 languages (English, German, Japanese, French, Spanish, Brazilian Portuguese, Polish, Korean, Italian, Dutch, Simplified Chinese, Traditional Chinese), with English as the fallback. PDF, CSV, Markdown and Rovo text stay as they are. Advanced adds a PDF auditor pack, which prints a Report SHA-256 and, from 2.1.0, an informational control mapping that may support evidence for SOC 2, ISO 27001:2022 and NIS2. The mapping is a supporting interpretation, not certification or an auditor's opinion. Advanced also adds an offline auditor ZIP with an offline hash-chain check, and a configuration documentation PDF of stored workflows, screens and notification schemes.
  • Drift against a baseline Advanced. Save a baseline of your configuration and see what drifted from it. Advanced also adds real-time alerts from watchlist rules (in the app or as Jira work items, including composite rules and quiet hours), a tamper-evident SHA-256 hash chain with verification, baselines as of a past date, ignored paths, template space baselines, a Health check (from 2.1.0 a finding can create one labelled work item), labels for Jira Automation, change request linking, periodic summaries, retention from 30 to 1,095 days, and a Rovo agent.
  • Runs on Atlassian, zero egress. No email, Slack, webhooks or other calls outside Atlassian. Data is stored in Forge SQL and follows your Jira site’s data residency. Only users with the Administer Jira global permission can open the app. The only writes are the alert and summary work items created in Advanced, in a space you choose. ConfigRadar never changes your Jira configuration.
  • It addresses the long-standing Jira Cloud gap tracked as JRACLOUD-74945.

Who it is for

ConfigRadar is built for Jira Cloud administrators who need a reliable record of Jira configuration changes, including before and after diffs. Only users with the Administer Jira global permission can open the app, the dashboard gadget and the Rovo agent. Advanced also includes a space-admin view for space administrators.

Jira Cloud has no complete before and after record of configuration changes, a gap tracked publicly as JRACLOUD-74945. The native audit log often records that an object was updated without the full state before and after. ConfigRadar turns the audit log, live events and daily snapshots into a reviewable change history that you can export for your auditors.

How it works

  1. Install it from Atlassian Marketplace. A Jira administrator adds it to a Jira Cloud site, and it appears under Apps in Jira administration. Only users with the Administer Jira global permission can open it.
  2. Let it collect history. On install, ConfigRadar backfills 30 days of the Jira audit log. It then imports the audit log on a schedule (hourly on paid plans; every six hours on free Standard for sites with up to 10 users), listens to live configuration events, and takes daily normalised snapshots of 22 object types (after a site administrator accepts version 2.0.0; until then, existing installs stay on 1.4.0).
  3. Review the timeline of Jira configuration changes, including the Jira custom field audit log and changes to workflows, schemes and permissions. Open any entry for the before and after, impact and revert steps.
  4. Use the weekly digest and export evidence as CSV. On Advanced, set watchlist rules and baselines, and export the PDF auditor pack.

Standard and Advanced

Standard includes scheduled audit-log history and live events, daily normalised snapshots of 22 object types (after a site administrator accepts version 2.0.0; until then, existing installs stay on 1.4.0), the change timeline, saved timeline views, before and after diffs, impact explanations, revert guidance, the weekly digest in the app, the dashboard gadget, CSV export, a UI in 12 languages (English, German, Japanese, French, Spanish, Brazilian Portuguese, Polish, Korean, Italian, Dutch, Simplified Chinese, Traditional Chinese) from the Jira user's language, and 90-day history.

Advanced adds real-time alerts from watchlist rules (in-app or as Jira work items, including composite rules and quiet hours), baselines and drift (a baseline as of a past date, ignored paths and template space baselines), a Health check, a tamper-evident SHA-256 hash chain with verification, the PDF auditor pack, change request linking, periodic summaries as work items, the Rovo agent, retention from 30 to 1,095 days, and a space-admin view.

Both editions run on Atlassian with zero egress, and both have a 30-day free trial. Standard is free for up to 10 users. For current prices, see the Atlassian Marketplace listing. The full comparison is in the documentation.

Where to install it

Install ConfigRadar from its Atlassian Marketplace listing. Setup steps are in the documentation, scopes and data flow are on the Security page, and more answers are in the FAQ.

Try it free

Who makes it

ConfigRadar is made by Radrly (Radrly Sp. z o.o.), the publisher of the Radrly family of Jira Cloud apps built on Atlassian Forge, including AccessRadar, LimitRadar, MarginRadar and CapRadar. Support is at support@radrly.com.

Frequently asked questions

What is ConfigRadar?

ConfigRadar by Radrly is a Jira Cloud app (Atlassian Forge) that tracks configuration changes: who changed which workflow, scheme or field, before and after diffs, alerts, drift against a baseline and a tamper-evident history.

How is ConfigRadar different from the Jira audit log?

The Jira audit log records that a configuration object was updated, often without the full state before and after. ConfigRadar imports the audit log on a schedule, adds live configuration events and daily normalised snapshots of 22 object types (after a site administrator accepts version 2.0.0; until then, existing installs stay on 1.4.0), and turns them into a filterable change timeline with readable before and after diffs, impact explanations and revert guidance. It keeps that history for 90 days on Standard and 30 to 1,095 days on Advanced.

Does data leave Atlassian?

No. ConfigRadar runs on Atlassian (Forge) with zero egress: no email, Slack, webhooks or other calls outside Atlassian. Data is stored in Forge SQL and follows your Jira site’s data residency. See Security.

Can ConfigRadar alert on changes?

Yes. Both editions show a weekly digest in the app with the last 7 days by severity and object type. Advanced adds real-time alerts: watchlist rules raise an in-app alert as soon as a watched object changes, and can also create a Jira work item in a space you choose so Jira notifies the right people. No alert is sent by email, Slack or webhooks.

Does ConfigRadar revert configuration changes?

No. ConfigRadar records and explains changes and shows revert steps; you make the change in Jira. ConfigRadar never reverts anything itself.

Where do I install ConfigRadar?

Install ConfigRadar from Atlassian Marketplace. A Jira administrator adds it to a Jira Cloud site; only users with the Administer Jira global permission can open it.

More Radrly apps for Jira