Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Cycle Time & Deployment Frequency Reports

We're excited to share that our customers now have access to two new reports that will give Open DevOps customers a whole new world of clarity and visibility to their software delivery process.

Six months ago, we released the cycle time and deployment frequency insights in the deployments view in Jira to help developers visualize and measure progress from idea through production. While having #allthedata is important, we’ve heard that customers want further detailed reports for each of these insights with even more relevant information about their software delivery.

From engineering managers to product managers to team leads, everyone will benefit from utilizing our new deployment frequency and cycle time reports. Making sense of all of your data is essential to know whether or not your DevOps practices are working for your team. The Cycle Time Report is ready to explore today, and Deployment Frequency Report will be available over the next few weeks. Read on to learn more!

Cycle Time Report



Cycle time, among many other important DevOps metrics, is the total time it takes work to get through your software delivery process from when developers make a commit to the moment it’s deployed to production. In other words, it’s the speed of your development. The new Cycle Time Report shows an overview of your team’s cycle time, broken down week-by-week, empowering you to understand how your cycle time trend is changing over time. This new report, shows you which issues in particular and contribute to your team's cycle time and which issues exceed the median, allowing you to better understand what causes bottlenecks. Additionally, managers can find the average review time for issues and the number of commits and PRs. The Cycle Time Report will live in the existing Reports section on your Jira account. Team leads who use this key visualization will understand where to direct their attention to improving their software delivery process and determining where problems occur. In this report, some things you’ll find useful:

  • Overall cycle time trend broken down by week

  • Indicators for any changes in the cycle time

  • Problematic or long-running issues (those that exceed the median?)

  • Average review time for issues

  • Number of PRs & number of commits

Deployment Frequency



Deployment frequency is the frequency of how often you deploy things. The Deployment Frequency Report helps you understand how many times your team deployed code, while also displaying deployment frequency in non-production environments. This new report will enable you to analyze risk in your deployment pipeline by showing batch sizes for deployments and how often your team ships value to your customers in order to understand how this is trending over time and whether any process changes you’re making are having an effect.

In this report, some things you’ll find useful include:

  • How often your team is deploying, week over week

  • How many issues are included in each deployment which helps with assessing your batch size

  • The ability to track how often the team is shipping to specific environments

Additionally, both of these reports support first and third-party tools such as Bitbucket Pipeline, Azure Pipelines, GitHub, GitLab.

Both cycle time and deployment frequency reports will be available for all teams using a scrum template and kanban in either team-managed or company-managed projects (formerly known as next-gen and classic projects). 

Lastly, please provide feedback in the product—we’re excited to hear what you think!

Screen Shot 2021-08-16 at 5.03.23 AM.png

Screen Shot 2021-08-16 at 5.05.49 AM.png



Log in or Sign up to comment

Any plans to include integrations for any other tools? We use  to build and to deploy.



Like # people like this
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 06, 2021

Hi @Simon Logan thanks for your question! We are currently in talks with a number of different partners, Drone in particular. Whilst I don't have any timing to share at the moment, keep a look out for updates soon!

Kind regards,


Like # people like this

Hello @whammy .

Very good video, I got a lot of value out of it.  

Would you happen to be able to find out how to pull the data in a cycle time report via the Jira Rest API?  I'm assuming it will be a combination of GET requests on the Jira endpoints.

My company is creating an agile app and we need the metrics that the cycle time report provides.

Any guidance you can provide will be greatly appreciated.

Is there a page with more details what's required get these reports working? For example, which fields and the recommended practices are needed to ensure the Cycle Time and Deployment Frequency reports populate correctly?

Hi @whammy ,

Was there any progress with a Drone integration?



AUG Leaders

Atlassian Community Events