Measuring Lead Time for Change

[Sarfraz Singh]

I'm looking to track the DORA metric in Compass for my components but Lead Time for Change is not present in the pre-defined metrics that Compass has. Development Tab in the JIRA has the information readily available. Can you suggest how I'm able to get it with repo in Bitbucket ?

[Oskars Laganovskis]

Hi @Sarfraz Singh ,

If you happen to have eazyBI for Jira installed, you might set up data import from DevOps tools and then you might get the DORA metrics already in the sample reports.

You might read more about the process of setting up data imports in the eazyBI documentation - DevOps data import into eazyBI 

You might read more about that "Average change lead time" report in eazyBI here - Average change lead time 

Regards,

Oskars / eazyBI support

[Ali Umut Terzi]

Hi there 👋

At the moment, Compass doesn’t natively include “Lead Time for Change” as one of its built-in DORA metrics.

Here’s why:

• The Lead Time for Change metric is calculated based on code commit → PR merge → deployment timestamps.
• This data currently lives within Bitbucket Pipelines and the Jira Development tab, but Compass doesn’t yet ingest that lifecycle data automatically.

If your repo is linked to Jira and your Jira issues are mapped to commits & deployments,
you can use Jira’s Development metrics as the source of truth for LTC.
Then connect your Jira project as a data source in Compass to visualize related activity (deployments, commits, etc).

 This won’t compute LTC automatically, but it provides the traceability context within Compass.