Backlog workitems (e.g. Features, typically ART Level) in ADO are synced to the ART Backlog board in piplanning.io. The ART and or the Team is typically defined by the ADO Area Path.
We support two cases:
Case 1: Your ART Level workitems are always in the ART Area Path and never in a sub-path (e.g. Team).
They would only reside in
/SAFe/Animals
/SAFe/Mountains
Case 1: Your ART Level workitems are in the ART Area Path and also in sub-paths. They would reside in the following ones
The would reside in:
/SAFe/Animals (ART)
/SAFe/Animals/Cats (Team)
/SAFe/Animals/Tigers (Team)
/SAFe/Animals/Lions (Team)
/SAFe/Mountains/Matterhorn (ART)
/SAFe/Mountains/MountEverest (Team)
Case 1: ART Level workitems in ART Area path only
In the piplanning session, on the backlog board config step, select the settings tab. Make sure that Synchronize piplanning.io Teams via Area Path is off.
Case 2: ART Level workitems in ART Area path and child-paths
In the piplanning session, on the backlog board config step, select the settings tab. Make sure that Synchronize piplanning.io Teams via Area Path is on.
Hints:
Only paths which are mapped to a team (ALM configuration -> Team Mapping) will be taken into account for sub-paths. Workitems assigned to a sub-path which is not mapped to any team, will not be synced to the app.
ART-Sessions: For each sticky-type, you should map the Area Path field to the path of your ART.
The sync is bidirectional:
When you assign a team in the app, it will change the Area Path in ADO to that teams sub-path
When you un-assign a team in the app, it will change the Area Path to the ART Area Path (Area Path mapped on the sticky-type in case of ART session)