Version 2.4.0 · Updated 16 October 2026 · Review ECOHELP-174628
QuantMatrix Change Freeze Compliance Monitor
Find Jira change activity inside a freeze window and export a readable evidence report. The app is read-only and uses your Jira permissions.
Start here: what counts as a change?
An ordinary Task is not automatically a change. Use the exact lowercase label change, or an issue type whose name contains Change, Mudança or Cambio. The created, updated or resolved timestamp must also fall inside your selected UTC dates.
Before you begin
- Install version 2.4.0 on your Jira Cloud test site.
- Use an account with Browse Projects and access to the test issue. Administrator status does not override issue security.
- No JSM project, external account or API token is required. A Jira Task with label change is sufficient.
Five-minute positive test
- Open an accessible test project in Jira. Create a Task named Freeze reviewer test.
- Open the saved Task. In its Labels field, type
change, press Enter and save. Reopen the issue to confirm the label persisted. - Note the UTC calendar date of the issue's created or updated timestamp. For a test created on 16 October 2026 UTC, use 2026-10-16.
- Open Jira → Apps → QuantMatrix Change Freeze Compliance Monitor.
- Select the same project where you created the Task.
- Set both Freeze start and Freeze end to the UTC date from step 3.
- Click Run analysis. Selecting the project alone does not run the report.
- Expect Issues scanned ≥ 1, Changes scanned ≥ 1, Freeze findings ≥ 1, and a row containing your test issue key. Created in freeze and Updated in freeze can both increase. Resolved in freeze stays 0 unless the issue has a resolution timestamp inside the window.
- Click Export CSV. Open the downloaded file and confirm its issue key and evidence columns match the report.
Understand each result
| Metric | Meaning |
|---|
| Issues scanned | Visible issues in the recent sample, including ordinary Tasks. |
| Changes scanned | Issues recognized by change type or label. |
| Freeze findings | Recognized changes with a timestamp inside the UTC window. |
| Resolved / Created / Updated in freeze | Separate timestamp signals. They are cards, not tabs; all need not be nonzero. |
If you see only Issues scanned
- If Changes scanned is 0, check the exact saved label
change or supported issue type. Summary text alone does not qualify. - If Changes scanned is positive but findings is 0, compare the issue's timestamps with the inclusive UTC dates.
- Confirm the project matches the test issue and that the same account can find the issue in Jira search. Allow Jira search indexing to finish, then rerun.
- The app reads up to 100 most recently updated visible issues and shows up to 50 findings. Older issues may be outside the sample.
Negative test and CSV
Set both dates to a day outside all timestamps of the test change, then click Run analysis. Changes scanned should remain positive, but that issue should no longer appear as a finding. A report without findings still exports a CSV containing its headers. Changing dates or project clears the previous report; run again before exporting.
Evidence scores and limits
- Resolved inside the window: 100; created: 80; updated: 50. The strongest matching score is displayed.
- An update timestamp is an activity proxy, not proof of a deployment or policy breach. Verify exceptions and implementation records.
- Dates include the entire UTC start and end days. An empty sample never certifies compliance.
- The app does not modify Jira issues or send issue content outside Atlassian. CSV is generated in your browser.
Support
If results still differ, provide the app version, issue type, sanitized label, UTC timestamps, selected dates and counts through the review ticket or support. Never include credentials or confidential issue text.