Track Lead Time to Change
Open
@dsilvam is already working on this.
Since Jan 27, 2025.
Team : Falcon
Type : Task
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Parent Issue
No response
Task
There is an engineering departamental rock which consist in tracking Lead Time to Change.
Lead Time To Change, from an engineering standpoint means the following:
- Time from a PR is sent (non-draft) to it gets deployed on a release that at least one customer is using
- Time from an GH issue is included in a sprint to it gets deployed on a release that at least one customer is using
Proposed Objective
Please Select
Proposed Priority
Please Select
Acceptance Criteria
Lead Time To Change properly tracked and giving results for each non-draft PR and GH issues included in sprints.
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.