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, 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 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!
Hello folks, This is a series of articles where I explain GitHub Script with GitHub Actions and how you can automate publishing data on Atlassian & GitHub Platform based on the results of Workf...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events