Capture and report Lead Time To Change

[dsilvam]

Parent Issue

No response

Task

This is the Epic to track the development of what's needed to track Lead Time To Change metric for issues and pull-requests.

Lead Time To Change for issues is tracked as the following:

Pre-conditions

• Issue belong to a closed Epic (feature flag turned on)
• Closed issue does not belong to an Epic (isolated issue not part of a big feature or big fix)

Start event: Issue being included in a Sprint. (Falcon, Scout, Platform, Support)
End event: Issue being labeled with "Customer Deployed"

Lead Time To Change is the time between the start event and the end event.

We need to report this time per issue and in average.

Lead Time To Change for pull-requests is tracked as the following:

Pre-conditions

• PR is linked to a closed issue that got released (Release label assigned)

Start events:

• PR is opened straight in Ready to Review state.
• PR is marked as "Ready to Review" from a previous Draft state.
  End event: The issue linked to the PR got release (Gets a Release Label assigned)

Lead Time To Change is the time between the start event and the end event.

We need to report this time per issue and in average.

Proposed Objective

Customer Success

Proposed Priority

Priority 2 - Important

Acceptance Criteria

Lead Time To Change metrics both for Issues and Pull-requests available to be captured and reported via script.

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response