Contents:
Hierarchy synchronization options
Overview
In order to take advantage of the desired structure sync between your story map and the Azure DevOps project you must start with setting up Azure DevOps integration for your board.
💡 Tip - Learn more about How to setup Azure DevOps integration for your story map
All level structure sync
By selecting the all level structure sync option you will link all three level of your story map to Azure DevOps as following:
This allows you to push top level cards from the story map to Azure DevOps as an epics. Second level cards as features and third level cards as user stories. You can also import cards from Azure DevOps to the story map and they will be placed in the structure if they have the right parameters set.
💡 Tip - Learn more about How to customize your Azure DevOps integration
Second level structure sync
By selecting the second level structure sync option you will link the second level cards and user stories on the third level of your story map to Azure DevOps as following:
Top level cards on the story map will be only placeholder cards. You can create as many top level cards you want on the story map and use them to organize or theme your cards on the board. Top level cards will have no impact in Azure DevOps if you use second level structure sync.
Only third level structure sync
Using the third level structure synchronization option, you can select the appropriate Azure DevOps work item type to use when exporting third level cards from StoriesOnBoard. This can be epic, feature, task, user story, issue. This means that you have no advantage of the board hierarchy as in the case of All or Second level structure synchronization.
Changing the hierarchy synchronization
Hierarchy settings are available on the story map: select the "Settings" menu then "Integration settings" to access it:
When you link more levels of the story map, choose the direction of the first synchronization: from StoriesOnBoard to Azure DevOps (your upper level cards are created as Epics and Features), or from Azure DevOps to StoriesOnBoard.
StoriesOnBoard tells you how many cards were pushed:
When you link fewer levels, StoriesOnBoard asks for confirmation before it unlinks the upper level cards from their work items.






