Product documentation · Updated 15 October 2026

Release Commitment Drift Auditor

Read-only Fix Version change evidence for Jira Cloud, implemented with Atlassian Forge.

How it works

Open Jira Apps → Release Commitment Drift Auditor, select an accessible project and click Run analysis. The read-only analyzer samples up to 100 recently updated issues, examines accessible Fix Version changelog history and ranks issues showing version assignment churn. Rows show additions, removals, changes, current version and days to release where Jira exposes a release date.

Transparent scoring

The score, capped at 100, adds 12 points per Fix Version history change, 8 per version addition, 15 per removal and a further 15 points within 14 days or 25 points within 7 days of a current release date. A high score is a review signal, not proof of misconduct or delivery failure.

Reviewer test procedure

In a disposable Jira Cloud test project, create a future-dated project version and an accessible test issue. Assign a Fix Version, then change or remove it so that its History contains at least one real entry. Open Jira Apps, select that project and click Run analysis. Verify the issue appears with a nonzero Version changes count and matching additions and removals. Download CSV and compare the issue key and score with the visible report. Repeat on a project with no Fix Version history and verify the empty report.

Installation and configuration

A Jira Cloud administrator installs the existing Release Commitment Drift Auditor listing from Atlassian Marketplace. During review use the existing distribution link supplied with the ticket. Open Jira → Apps → Release Commitment Drift Auditor, allow the Forge user consent prompt if shown, and select a project. No external account, credentials or server configuration are required. Analysis is read-only and does not enforce a release commitment policy.

Requirements and permissions

The reviewing user needs Browse Projects and visibility of the test issues. Admin rights do not override issue security. The inspected manifest enables Forge licensing and requests read:jira-work. The resolver reads Jira asUser() and does not modify projects or issues. No separate QuantMatrix account is required.

Limits and troubleshooting

The scan is limited to 100 recently updated visible issues, up to five bulk changelog pages and 50 displayed findings. A blank report is not certification of release stability. Confirm issue history and project visibility when findings are absent. If analysis fails, check Forge consent, Jira permissions and API availability. Browser CSV downloads may require permission.

Support and privacy

Contact support@quantmatrixintelligence.com with non-sensitive reproduction steps. Do not send passwords, API keys or customer content. Visit /support and /privacy for support and security information. The inspected manifest declares no remotes.

Support · Privacy & security