Map Iterations to Area Paths (Teams)
Create or edit a PI session
Make sure that you have included the teams you have previously mapped to area-paths
In the last step of the PI session configuration you can now map teams to iteration-paths
If you have multiple area-paths for one team, you have to set the iteration-path for each area-path as well
Synchronize iterations for Backlog level work items
For your work items managed on Backlog level you can synchronize the Iteration field. Depending on the iteration in which a Backlog level sticky type is planned, the iteration is synchronized back to ADO based on the iteration paths which are defined for your teams.
To enable synchronization, check the corresponding box under the Backlog Board configuration.
Iteration path filtering
In case you do not specify an iteration-path for the sticky-type: It will get every feature in to the app which matches the field-filter criteria and therefore any workitem (no matter of the area-path value) will appear.
In case you do specify the iteration-path: Every feature which matches the iteration-path of the sticky-type OR matches any of the defined iteration-paths of any team (of the same ART) defined in the cockpit (Iteration screen) will appear. Keep in mind that the team iteration-path needs to be a subpath of the iteration-path defined on the sticky-type or it will not be included.
In case of a sticky-type with iteration-path = “Futurama/PI1“
Only team iteration-paths which are bellow “Futurama/PI1“ will be taken into account.
Will be included:
Will NOT be included:
Example
"Another nice Feature" pulled in and visualized on the Program Board for planning.
Feature planned delivery in Iteration 1
