Median Lead Time for Changes: how to configure for GitFlow

[jvgr019]

Hello,

We have a question regarding the calculation of the "Median Lead Time for Changes" metric.

It seems that the metric is being calculated based on pull requests merged into the repository's default branch (in our case, develop, which is configured as the main branch in Bitbucket how recommend GitFlow strategy).

However, our actual production branch is master. Our workflow is GitFlow:

• Developers merge changes form features branches into develop.
• Develop is the main branch configured at bitbucket
• Changes are later promoted to master throw release
• Only when code reaches master do we consider it deployed to production.

Because of this, the current calculation appears to underestimate the real Lead Time for Changes. For example, repositories with a high volume of activity on develop are showing an "Elite" Lead Time (less than 2 hours), even though the changes have not yet reached the production branch (master).

Could you clarify:

1. Is the Median Lead Time for Changes calculated using the repository's configured main/default branch?
2. Is there any way to configure a different target branch (such as master) for this calculation?
3. If not, are there any recommended approaches for teams whose production branch differs from their default branch?

Thank you.