Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your existing Jira Software Cloud site 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.
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
A project administrator can enable the Reports feature from the Project settings.
To view the cycle time report,
In the company-managed project, navigate to the Reports > DevOps section.
In the team-managed project, navigate to the Reports > Overview section.
Reading the cycle time report
Understand the weekly comparison chart
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
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 section displays issue data, which can be sorted by highest to lowest cycle time or pull request (PR) review time.
After the launch of the Cycle time report, you cannot see the review time until sufficient historical data is gathered for your PRs. Hence, if you select a week prior to the launch date, the Issues shipped table won’t have any data in the Review time column.
Ways to reduce your cycle time
Starting small and fast: You can deliver more by 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 PRs: Breaking the work items into smaller chunks and iterating frequently enables the 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 cover the use cases that help build a high-quality product and aid in creating a future-proof holistic solution.
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.
For additional information on the deployments insights, see Enable deployments.
Was this helpful?