### Release notes New stage events for custom Value Stream Analytics To improve the tracking of development workflows in GitLab, we added the Value Stream Analytics has been extended with a new stage event: "Issue first associated with an iteration". This event can be used to detect problems caused by teams planning too far ahead (not being agile) or issues rolling over from iteration to iteration. For example, you can now add a "Planned" stage that starts when "Issue first associated with an iteration" and ends when the "Issue first assigned". ### Problem to solve For teams that use iterations, adding an issue to an iteration is when it is considered "Planned". This is an important milestone in the lifecycle of an issue and can detect problems with teams planning too far ahead (not being agile) or issues rolling over from iteration to iteration. ### Proposal In Value Stream Analytics, add a new `start event` called "Issue first associated with an iteration", similar to "Issue first associated with a milestone". | VSA start events dropdown (current)| | ------ | |  | ### Intended users - [Delaney](https://about.gitlab.com/handbook/product/personas/#delaney-development-team-lead) - [Parker](https://about.gitlab.com/handbook/product/personas/#parker-product-manager) ### Feature Usage Metrics ### Does this feature require an audit event? <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *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.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->