Pull request cycle time different periods

[joshalexandre]

We love the "Pull request cycle time" metric under Jira > Development > Key metrics.

We'd like to zoom out and see it over a broader period (weekly, quarterly, etc).

Is that possible?

[Birkan Yildiz _OBSS_]

Hey @joshalexandre

Native Jira's metrics are great for a quick pulse check, but they generally rely on fixed rolling windows and don't allow you to easily "zoom out" to analyze historical trends over custom periods.
If you are open to using a marketplace app, and if your pull request and review process is mapped to your Jira workflow statuses, you can track these exact trends over broader periods using Timepiece - Time in Status for Jira.

Here is how you can set it up to see weekly, quarterly or yearly trends:

Define Your Metric: Use the Status Duration report and use the Consolidated Columns feature to group your PR-related workflow statuses together into a single "PR Cycle Time" column.

Get the Average: Change the report option from a standard list to an Average report.

Group by Period: This is the magic step. Use the Group By dropdown and select a date field like Created (WEEK) or Created (MONTH). This instantly generates a trend report showing how your average cycle time fluctuates week-over-week or month-over-month.

You can also visualize this data using bar or line charts and put it directly on your Jira dashboard to track your team's efficiency over time.

Hope this helps. You can visit Timepiece’s Atlassian Marketplace page to learn more. Please let me know if you have any further questions.

Disclosure: I am part of the OBSS team, the creators of Timepiece.

Best,
Birkan

[Anastasiia Maliei SaaSJet]

Hi @joshalexandre

Jira’s built-in Pull request cycle time metric is useful, but it’s quite limited if you want to zoom out and analyze the trend over longer periods.

If your team reflects PR or code review work in Jira workflow statuses, Time Metric Trend Gadget can help with this. You can create a workflow-based metric such as Code Review time, PR Review time, or overall Cycle Time, and then display it as a trend over time using configurable time ranges and buckets, for example weekly.

It won’t directly extend Jira’s native Development → Key metrics → Pull request cycle time, because that metric is based on Jira development data. But it can give you a broader workflow-level trend and help you understand how review or delivery time changes over time. You can also drill down into the work items behind each point on the chart.

Try app Time Metric Tracker