Product documentation · Updated 14 October 2026

Approval Wait-State Analyzer

Measures time spent in approval-like Jira statuses, repeated entries into approval and current waiting state.

How it works

Reads status changelog segments for the selected issues (up to five bulk changelog pages). Names matching approval/approve or Portuguese approval terms are recognized. The report shows total wait, longest wait, entry count, current waiting state and a wait score. The score is capped at 100: rounded longest wait hours × 2, plus 8 for each additional entry.

Reviewer test procedure

1. Use an isolated test project with a status named Waiting for approval or Aprovação.
2. Move a test issue from a non-approval status into that status; keep it there for the active-wait case. For the completed case, move another issue into and then out of approval. Use existing timestamped history for meaningful duration values.
3. Run analysis. Verify the approval issues appear, active status shows Waiting now = Yes, and recorded segments contribute to wait hours. Newly transitioned issues may show rounded zero hours.
4. Export CSV and compare issue keys and wait columns against the visible table.
5. Run on a project whose issues have neither approval history nor current approval status: expect no finding rows.

A current approval status with no visible entry history may appear with zero measured duration; the app does not invent an entry timestamp.

Requirements and installation

A Jira Cloud site, access to the selected project and permission to browse its issues are required. A Jira administrator installs the existing app from its Marketplace listing or the existing private installation link during review. Open Jira → Apps → the product name. Allow the Forge user access prompt if shown. No separate QuantMatrix account or third-party credentials are required.

Usage

1. Open the app from Jira Apps.
2. Select an accessible project from the dropdown.
3. Click Run analysis; selecting a project alone does not run the report.
4. Review the metric cards, findings table and Method section.
5. Click Export CSV when findings exist. A project with no matching rows correctly leaves export disabled.

Permissions and data handling

The inspected manifest declares read:jira-work. The resolver uses Forge asUser() and respects the current user's Jira access. This implementation reads Jira data and does not edit issues. No remotes or external customer-data egress are declared in the inspected manifest. CSV exports are generated in the user's browser; handle downloaded files according to your organization's policy.

Limits and troubleshooting

The scan reads at most 100 recently updated issues and displays up to 50 finding rows. Results are evidence and heuristics, not autonomous workflow enforcement. If no projects appear, check Jira project access. If an API error appears, record the error, product name and time and contact support without sending credentials or sensitive issue content. An empty findings table is expected when no eligible data exists.

Support

Submit a support request · support@quantmatrixintelligence.com. Include the product name, version, reproduction steps and non-sensitive error details.