The iteration kind in ADO only returns iteration metadata (e.g., current, past, future, sprint names) without any associated work items. This limits its usefulness for teams that want to track the actual work within an iteration, rather than simply replicate Azure DevOps board structure in Port. While the WIQL workaround ( @CurrentIteration('[MyProject]\\[MyTeam]') ) partially addresses this, it requires hardcoding a specific project and team, making it inflexible and difficult to scale for organizations with multiple teams. Requested Behavior Introduce a new capability, either as a separate kind or an enhancement to the existing iteration kind —that leverages the Get Iteration Work Items endpoint [ https://learn.microsoft.com/en-us/rest/api/azure/devops/work/iterations/get-iteration-work-items?view=azure-devops-rest-7.1&tabs=HTTP ] to retrieve work items associated with a given iteration. This would enable use cases such as: Viewing all work items in the current sprint across teams Comparing work items across past and future iterations Building dashboards that reflect real-time sprint progress
