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

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

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.

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.