Product documentation · Updated 14 October 2026

Intake Quality Gate for JSM

Scores the completeness of service requests and highlights missing intake signals. The gate is advisory: it does not block or modify requests.

How it works

Each request receives a score out of 100: summary of at least 15 characters (10), description of at least 40 characters (30), priority (10), attachment (15), component (10), label (5), environment/context of at least 10 characters (10), and reporter (10). Gap score = 100 − quality. Lowest-quality rows appear first.

Reviewer test procedure

1. Use an isolated JSM project with two accessible test requests.
2. Create one request with a short summary and no description, attachment, component, label or environment. Leave any Jira-required fields set.
3. Create another with a descriptive summary and description over 40 characters, priority, a harmless attachment, component, label, environment over 10 characters and reporter. Ensure those fields are supported by the test project.
4. Select the project and click Run analysis. Verify both rows appear and the second scores higher; use the displayed missing-signal list to explain fields your project cannot supply.
5. Export CSV and compare issue keys, Quality, Gap score and Missing signals with the table.
6. Confirm neither request was changed by the scan.

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.