QuantMatrix Intelligence

Cost-to-Serve Signals for Jira Service Management

Read-only analysis of visible Jira Service Management work. The app shows recorded work hours by Jira issue type, missing time-record coverage and optional estimates calculated only from recorded hours and the rate chosen by the user. It is not an invoice audit or a claim of cost savings.

Requirements

A Jira Cloud site with Jira Service Management, an accessible service project, permission to browse its issues, and this app installed in the Jira site. No separate QuantMatrix login is required.

Getting started and checking your results

  1. In an authorized JSM test project, create or select a Jira issue labeled Service Request.
  2. Use Jira Log work to record exactly 1 hour 30 minutes on that issue. Confirm the Jira timespent field is 5400 seconds.
  3. Open Jira → Apps → Cost-to-Serve Signals for Jira Service Management. Select the JSM service project.
  4. Leave Hourly Cost empty. Click Analyze visible issues; do not expect the dropdown selection alone to run the analysis.
  5. Find the test issue in the issue evidence and the corresponding Jira issue type group. Expected recorded hours for the single issue: 1.5.
  6. Enter 120 in the hourly-cost field and BRL for currency, then analyze again. Expected estimated recorded-labor cost for that single issue: BRL 180.00.
  7. Export CSV, then compare the issue key, logged hours and displayed estimate with the source Jira issue. Other issues in the project can change aggregate totals.

What to expect in special cases

  1. JSM issue without time logging: the individual issue should show Not recorded, not a fabricated work duration or cost.
  2. JSM project with no visible issues: empty results are expected, with no claim that work never occurred.
  3. Jira Software project instead of JSM: the server rejects this project type.
  4. Project with more than 100 recently updated issues: the report must show the partial-sample warning, not imply complete coverage.
  5. Restricted user: only issues permitted to that Jira user should contribute; verify by comparing results against the same user’s access.
  6. Blank hourly rate: no monetary estimate. Invalid or negative rates should be rejected.

Explanations and data limits

Only the 100 most recently updated visible service issues are sampled in one scan. Jira timespent may be missing even when work occurred. Elapsed days, priority and optional labels are separate, transparent friction heuristics; they are not verified hours or financial losses. The app makes only read-only Jira requests under asUser and exports CSV on the user device.

Troubleshooting

If no projects appear, check that the account has access to a Jira Service Management project. If the result is empty, verify the test issue has a worklog and is among the recent visible issues. For API errors, send only the error class, site type and app version to support; never send passwords, tokens or sensitive customer issue data.

Support and policy

Support portal · support@quantmatrixintelligence.com · Product privacy information