Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Create powerful rules to start automating your manual, repetitive processes.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
This page is for team-managed projects
If the lower-left of your project sidebar says you're in a company-managed project, check out these company-managed project articles instead.
Learn more about the difference between company-managed and team-managed projects.
The deployment frequency report helps you understand how many times your team deploys code to production. The report also shows the deployment frequency in non-production environments.
It allows you to analyze risk and how often you are shipping value to your customers.
Before you begin
Connect your source code management and CI/CD tools
Your Jira admin needs to have Jira integrated with your CI/CD pipeline. This allows you to receive the deployment data from your connected tools such as Jenkins, CircleCI, or Bamboo. Learn more about how to use Jira for CI/CD.
Make sure you have enough production deployment data
To view this report, you need deployment events from your CI/CD tool and commit events from your source code management tool. You must also include issue keys in your branch names, commit messages, and pull requests. Learn how to reference issues in your development work.
Check your project and issue-level permissions
You need View development tools permission to view the deployment frequency report. Learn more about enabling permissions for your team-managed projects.
Only the project admin can enable the Reports feature from the Project settings.
View and understand the deployment frequency report
To view the deployment frequency report:
If not already there, navigate to your team-managed Jira Software project.
From your project’s sidebar, select Reports > Overview > Deployment frequency report.
The deployment frequency report contains the following sections:
Select a timeframe from the date selector filter to view deployments for the week of your choice.
Weekly comparison: The bar chart shows the average production deployments over the past 12 weeks. The line chart shows the median issues per production deployment (batch size) over the past 12 weeks.
All deployment environment types: This line chart shows the weekly deployments per environment.
Week breakdown: This scatterplot shows the breakdown of weekly production deployment as compared to the batch sizes.
Deployments: This table shows your deployment data.
Deployment navigator: This screen shows the Jira issues that were included with each deployment.
Understand the weekly comparison charts
You can compare both charts to understand the correlation between batch size and deployment frequency. Deployments with large batch sizes tend to be riskier. To avoid risky deployments, try to deploy to production more often or equally to other environments.
Compare all deployment environment types
If you have high deployment frequency in non-production environments, you need to automate ways to deploy more in production. More frequent deployments help your team iterate quickly, catch bugs faster, and tighten your development loop.
View weekly deployment data
Each deployment provides you with information on:
Jira issues per deployment
Gain insights into each deployment
Select the issues in the table to see the Deployment navigator, which shows you details of the issues included with your deployment.
Different ways to improve your deployment frequency
Implementing Continuous Integration and Continuous Deployment practices helps you increase software delivery speed.
Reducing the batch size also reduces the risk of deploying code to production.
Deploying more often in the production environment reduces your lead time for shipping changes.
Automating the development process helps your team deliver value to your customer faster.
Was this helpful?