VSA - Iteration start event for issue
Release notes
Problem to solve
For teams that use iterations, when an iteration that the issue is assigned to starts, work for that issue begins. This is an important milestone in the lifecycle of an issue and can detect problems with issues rolling over from iteration to iteration.
Proposal
Add to capture that an "Iteration began" to value stream analytics. This captures the first time an assigned iteration starts to measure rollover properly.
For example:
- An issue is loaded into an iteration that starts on Jan 15, 2024 on January 1, 2024.
- When the iteration begins on Jan 15, 2024, there should be an event to say that this issue was part of an active iteration.
This will differ from "added to iteration" since that captures when it was added to any iteration, whether it is active or not. In the example above, the "added to iteration" event value will be January 1, 2024.
Intended users
Feature Usage Metrics
Does this feature require an audit event?
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.