Key metrics on the Development page
This feature is currently in beta.
This means that the feature may not be available to everyone, the functionality may be limited, and it will change as we continue to develop it.
Key metrics provide a snapshot of your team’s software delivery health. These metrics help you quickly see how your team is tracking, what’s progressing, and where work might be stuck. For example, if you notice a spike in open bugs or slow pull request reviews, you’ll know where to investigate further. By surfacing trends and potential risks early, you can make informed decisions and keep your team’s momentum high.
This page describes the key metrics available on the Development page in Jira.
Work items completed
The work items completed metric shows the number of work items completed in your Jira project each week from Monday to Sunday. A work item is counted as complete if its status is in the ‘Done’ category at the time the metric is accessed.
The metric displays data for the previous seven weeks and the current week. The data for the current week reflects the work items completed during the week and is continuously updated until the end of the week.
No setup is required—data appears automatically as your team marks work items as done.
Work items at risk
The work items at risk metric indicates the number of overdue or reopened work items, helping you spot potential problems or roadblocks that could impact software delivery success.
Overdue work items
The overdue work items count indicates the number of work items that are past their due date and their status doesn’t fall in the ‘Done’ status category. Overdue work items may need follow-up to keep work on track.
The count includes all currently overdue work items in your project.
To use this metric, add the due date field to your work items and set due dates. The count updates automatically as items become overdue.
Reopened work items
The reopened work items count indicates the number of work items that were previously marked with a status belonging to the ‘Done’ category, but have moved back to a status belonging to the ‘To do’ or ‘In progress’ categories.
The count includes all currently reopened work items in your project and updates automatically when any work items are reopened or done—no additional setup is required.
Open bugs metric
The open bugs metric indicates the number of bugs in your project that are not yet done, for example, have a status belonging to the ‘To do’ or ‘In progress’ status categories.
The count updates automatically as bugs are created, fixed, or closed—no additional set up is required.
The metric helps you keep track of your team’s bug rate, spot trends, and take action if needed.
You’ll see this metric only when no CI/CD tools are connected to Jira. If you connect a CI/CD tool, like Bitbucket Pipelines or Jenkins, you’ll see the deployment frequency metric instead.
Pull request cycle time
The pull request cycle time metric indicates the median time for pull requests to go from first commit to being merged. It accounts for all pull requests linked to work items in your project that were merged in the past seven days.
The metric indicates the efficiency of your team's code development and review process.
To see pull request cycle time metric, your Jira admin must connect your development tool to Jira, and your team must link pull requests to work items in your project.
Lead time for changes
The lead time for changes metric measures the duration from when a code change is committed to your branch until it reaches a deployable state. For instance, this occurs when the code successfully passes all required pre-release tests.
To see this metric, set up your deployment integration and link the development activity to Jira using work item keys. Then run at least one deployment on a linked branch, commit, or pull request.
Deployment frequency
The deployment frequency metric indicates the average number of production deployments per week, calculated across 12 weeks, including the past 11 weeks and the current week.
Deployment frequency measures how often production deployments occur. This metric helps teams understand how frequently they are delivering changes to customers and is a key indicator of software delivery velocity and DevOps performance
To see this metric, set up your deployment integration and link the development activity to Jira using work item keys. Then, run at least one deployment on a linked branch, commit, or pull request.
Find out how to send deployment information to Jira
You’ll see this metric will only when CI/CD apps, like Bitbucket Pipelines or Jenkins, are connected to Jira. If you don’t have any CI/CD apps connected, you’ll see the open bugs metric instead.
Compass scorecards metric
The Compass scorecards metric displays the health of your software components cataloged in Compass based on the scorecards applied to them.
To see this metric, set up Compass, add your components, apply scorecards, and link them to your Jira project. The metric shows the status for the top two scorecards applied to linked components.
Your access to scorecard data in Compass depends on your Compass user role. The Compass scorecard metrics on the Development page will display data only from the scorecards you are permitted to view.
Was this helpful?