Work Items Count Metrics

Work Item Count Metrics measure the number of distinct Jira work items that meet a defined set of conditions.
These Metrics focus on counting work items based on events or states, without considering effort, duration, or story points.

They help teams understand how work flows through the system at a high level.

What You Can Analyse with Work Item Count Metrics

Work Item Count Metrics are commonly used to analyse:

  • Demand and intake — how many work items are being created?
  • Delivery outcomes — how many work items are completed or resolved?
  • Backlog size — how many work items are currently open?
  • Flow stability and change — how often are work items reopened?

How Work Item Count Metrics Differ

Although all Work Item Count Metrics count work items, they differ based on what qualifies a work item to be counted.

Depending on the Metric, work items may be counted based on:

  • Events — when a specific event occurs (e.g. when a work item is created or resolved)
  • Lifecycle transitions — when a work item moves between key workflow states (e.g. when it transitions into a completed state)
  • State at a point in time — the status of work at a given date/time (e.g. work items that are currently open)

Completed vs Resolved — What's the Difference?

Two Metrics in this category are easy to confuse:

Work Items Resolved uses Jira's native Resolution Date — the date the Resolution field was populated. This is set by your Jira workflow and reflects when Jira considers the issue "done" at the field level.

Work Items Completed uses Lifecycle Mapping — it counts work items that have entered a status you have mapped to the Completed lifecycle state in Dashlytics App Settings. This gives you control over what "completed" means, independent of Jira's Resolution field.

Use Work Items Resolved when you want to track Jira-native resolution events. Use Work Items Completed when you want delivery metrics based on your own lifecycle definition.

Choosing the Right Metric

Each Work Item Count Metric is designed to answer a specific question. Choose the Metric that best matches the insight you are looking for:

  • Work Items Created — use this to understand incoming demand over time
  • Work Items Resolved — use this to track when work items are marked as resolved using Jira's Resolution field
  • Work Items Completed — use this to measure delivery outcomes based on your Lifecycle Mapping
  • Work Items Closed — use this to analyse when work items are formally closed in their lifecycle
  • Active Work Items — use this to understand work currently in progress (started but not yet complete)
  • Unfinished Work Items — use this to track all work that has not yet reached completion, including not-started and in-progress items
  • Work Items Overdue — use this to count work items that are past their due date and not yet completed
  • Work Items Reopened — use this to identify rework and flow instability

Metrics in this category

For AI agents: the complete documentation index is available at https://dashlytics-docs.vivek-fitkariwala.workers.dev/llms.txt, the full documentation bundle is available at https://dashlytics-docs.vivek-fitkariwala.workers.dev/llms-full.txt, and this page is available as Markdown at https://dashlytics-docs.vivek-fitkariwala.workers.dev/reference/metrics/work-items-count-metrics/index.md.