Imua Delivery Metrics for Jira

Understand where delivery friction is showing up in your Jira workflow.

Imua Delivery Metrics uses Jira delivery history to explain how work is moving through your system, where flow is being disrupted, and what your team may need to examine next.

The app focuses on system conditions, not individual performance.

Available in the public beta

Blocked-Work Drag

Shows how much delivery time is being consumed while work is blocked.

Blocked-Work Drag helps teams understand whether blocked work is taking up a meaningful share of active delivery time. It explains what the available evidence shows, what limits the finding, and which blocked items may be worth examining.

Flow Pressure

Shows whether work is entering the delivery system faster than the team is finishing it, causing unfinished work to build up.

Flow Pressure helps teams see whether accumulation appears temporary or may be persisting over time. It also explains when the available delivery history is not yet sufficient to support a conclusion.

Priority Movement

Shows how often work changes position after delivery has begun, which may indicate unstable priorities or disrupted execution.

Priority Movement helps teams examine whether in-progress work is frequently being reordered and whether those changes may be interfering with delivery.

Additional delivery metrics

These metrics are part of the broader Imua delivery-metrics model but are not included in the current Jira Marketplace public beta.

Carryover / Spillover

Shows how often work expected to finish within a delivery period remains unfinished and carries into a later period.

This can help teams examine whether delivery plans regularly exceed available capacity, whether work is entering too late, or whether items are larger or more uncertain than expected.

Rework / Reopen Signal

Shows how often completed work returns to an active state or requires additional work after it was considered finished.

This can help teams examine unclear completion standards, missed requirements, quality issues, or work that is being closed before it is truly complete.

Scope Instability

Shows how much the committed delivery scope changes after a delivery period has begun.

This can help teams examine whether new work is frequently being added, planned work is being removed, or the delivery commitment is changing too often to provide a stable basis for execution.

What each metric explains

For each available metric, Imua Delivery Metrics provides:

  • What this metric means
  • What we found
  • What limits this finding
  • What to examine next
  • Result quality
  • Supporting evidence

When the available Jira history is too limited to support a reliable conclusion, the app says so rather than presenting an unsupported result.

Result quality

Delivery metrics depend on the amount and quality of the Jira history available.

A result may be limited when:

  • too few eligible issues are available;
  • the observation period is too short;
  • workflow history is incomplete;
  • required delivery signals cannot be established; or
  • the available work is not representative of the broader delivery system.

Imua Delivery Metrics explains these limitations alongside the result.

Installation and access

A Jira administrator installs and authorizes Imua Delivery Metrics through Atlassian.

After installation, open Imua Delivery Metrics in Jira and select the delivery context you want to examine. The app uses authorized Jira history to calculate and explain the available metrics.

The current version supports Jira Cloud.

Data and privacy

Imua Delivery Metrics accesses the Jira delivery information needed to calculate and explain its metrics.

We do not sell Jira data, use it for advertising, or design the app to evaluate individual employee performance.

Read the full Imua Systems Privacy Policy.

Public beta

Imua Delivery Metrics is currently offered as a free public beta.

Features, metrics, and presentation may change as we learn from real customer use. Feedback from beta users will help determine what Imua improves and releases next.

Support and feedback

For installation help, product questions, or feedback, contact:

jim@imuasystems.com