• Products
  • Documentation
  • Resources

Jira Automation docs have moved

All content related to Jira Cloud Automation, previously under the Automate your Jira processes and workflows section, have moved to the new Cloud Automation docs.

Go to Cloud Automation documentation | Why did we do this?

View and understand your deployment insights

The insights panel in the Deployments view shows the following metrics:

  • Deployment frequency - how often your team deploys code to production.

  • Cycle time - how long it takes for your team to ship issues through the deployment pipeline.

Screenshot showing the insights panel including deployment frequency and cycle time
  1. Insights panel: Select the Insights button on your view to show the insights panel. All insight cards are found here. To refresh the data, click the circular arrow icon.

  2. Insight card: Each insight is allocated a card that contains real-time data based on your team’s work. Insight cards also include visualizations and callouts that relate to the metric on the card.

  3. Feedback card: Provide feedback about Insights to help make this feature work best for you and your team.

How are deployment insights calculated?

Deployment frequency is the number of times your team deploys code to production. This insight shows your total deployments per week and calculates your average weekly deployments based on the last 12 weeks. It also compares your current weekly deployments to the 12-week average.

To determine an average, we need at least 4 weeks of data from the last 12 weeks. If you don’t see an average, you’ll need to wait until we have more data.

If you see something like this

It means this

Deployment frequency insight card showing no data


Your project hasn’t received any deployment info for 12 weeks, so there’s no data for us to show.

Deployment frequency insight card showing no average


Your project has received deployment info in the last 12 weeks, but there isn’t enough data yet to calculate your average weekly deployment frequency.

Deployment frequency insight card showing average deployments per week


Your project has received at least 4 weeks' worth of deployment info in the last 12 weeks, so we have enough data to calculate your average weekly deployment frequency.

 

Cycle time is measured as the time it takes an issue to transition from the first commit until the code is shipped. This insight shows your median cycle time per week, and calculates your overall median from the last 12 weeks. It also compares the current week’s median cycle time to the 12-week median.

To determine a median, we need at least 4 weeks of data from the last 12 weeks. If you don’t see a median, you’ll need to wait until we have more data.

If you see something like this

It means this

Cycle time insight card showing no data


Your project hasn’t received deployment and dev info in the last 12 weeks, so there’s no data for us to show.

Cycle time insight card showing no median


Your project has received deployment and dev info in the last 12 weeks, but there isn’t enough data yet to calculate an overall median cycle time.

Cycle time insight card showing weekly median


Your project has received at least 4 weeks' worth of deployment and dev data in the last 12 weeks, so we can calculate your overall median cycle time.

Additional Help