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.
Search for issues, navigate to your work, use advanced search, and work with your search results.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
The cycle time report helps teams understand how much time it takes to ship issues through the deployment pipeline and how to deal with outliers.
In this article you'll learn:
How to view and understand the cycle time report
What are ways to reduce your cycle time
How to spot and investigate outliers
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 aggregated data and View development tools permissions to view the deployment frequency report. Learn more about enabling permissions for your company-managed projects.
Only the project admin can enable the Reports feature from the Project settings.
Reading the cycle time report
To view the cycle time report:
If not already there, navigate to your company-managed Jira Software project.
From your project’s sidebar, select Reports > DevOps > Cycle time report.
Understand the weekly comparison chart
Customize your report by applying the Issue type and the Epic filters to laser focus your project’s cycle time.
The weekly comparison chart is a larger version of the cycle time insights from the Deployments view. It shows the median cycle time of one week compared to the 12 weeks prior.
Here, we're measuring an issue’s cycle time from the first commit until the code is shipped. If the issue is deployed more than once, the cycle time report will capture the most recent one.
Select a week to see the cycle time report of the issues that were deployed to production.
Analyze the weekly trend chart
Select a timeframe from the date selector filter to view issue data for the week of your choice.
The cycle time report uses a scatterplot to represent all issues that were shipped during the selected week. It displays a cycle time trend, and whether it is under or over the weekly median.
Ship your issues
The Issues shipped table displays issue data, which can be sorted by highest to lowest cycle time or pull request (PR) review time.
You cannot see the review time until sufficient historical data is available for your PRs.
Spot and investigate outliers
Outliers in your weekly trend chart
When you see a sharp increase in the median cycle time, it’s considered an outlier. Although you may be able to close issues, you must not overlook a spike in your cycle time.
Use the weekly comparison chart to reflect on what happened during the cycle time and lead time in your pipelines.
Drill down to your issues and analyze the bottlenecks to get insights into deployments.
Different ways to reduce your cycle time
Starting small and fast: You can deliver more by limiting work in progress, starting with smaller sprints and producing customer deliverables quickly.
Automate, automate, automate: Use automated tools to save efforts and delivery time. You can implement continuous integration through automated releases and invest the remaining time in coding.
Slicing the giant PR: Breaking the work items into smaller chunks and iterating frequently enables your team to perform better. It also reduces the review time for the pull requests significantly.
Assess the impact: Ensure the product value for the customer and whether the market analysis will help you foresee the impact way before the release.
Test-driven development: It will help cover the use cases that help in building a high-quality product and also in creating a future-proof holistic solution.
Was this helpful?