Contents:
How to access Azure DevOps integration settings
Open your story map
Go to "Settings"
Select "Integration settings"
You will be redirected to the Classic story map interface
Who can access or modify Azure DevOps integration settings
Only the Subscription Admin and the Story Map Admin can access the Azure DevOps integration or make changes. If you are a Member holding Editor rights on the story map and you may need to update the Azure DevOps integration settings, please contact the Admin of the story map.
💡 Tip - Learn more about How to setup integration with Azure DevOps
Azure DevOps integration settings
General settings
Disable synchronization
Use the disable/enable synchronization if you want to refresh the board
If you as an Admin of the story map wants to block the team from importing items
Use it if you want to refresh your status mapping settings
Disconnect Azure DevOps
In case you disconnect your story map from Azure DevOps, items no longer will be synchronized between your story map and the Azure DevOps project.
Once you need to connect your story map once again to an Azure DevOps project, you will need to setup the integration again for the story map.
Using disconnect Azure DevOps will only unlink this particular story map from Azure DevOps.
💡 Tip:
In case you link the story map once again to the same Azure DevOps project, all cards' link on the board will be reinstated.
Hierarchy synchronization
Integrating your story map with Azure DevOps you can select the integration mode for your hierarchy between StoriesOnBoard and Azure DevOps.
💡 Tip - Learn more about Hierarchy synchronization options with Azure DevOps
You can select the right hierarchy synchronization option according to your needs:
Link all level of the board hierarchy (Epic - Feature - User Story)
Link the second and the story level of the board hierarchy (Feature - User Story)
Link only story level cards
Status mapping
Setup status mapping between Azure DevOps and StoriesOnBoard to stay up-to-date at all time as issues are changing during execution. StoriesOnBoard identifies the workflow of your Azure DevOps project and you can match Azure DevOps statuses with your statuses on the story map.
In case your Azure DevOps project has a custom workflow that requires additional status values to be created on the story map, you can create your custom workflow on StoriesOnBoard as well.
⚠️ IMPORTANT ⚠️
Please note once you established the connection between StoriesOnBoard and Azure DevOps, card statuses will be only editable from Azure DevOps. This is a built in security to allow teams to execute the project without any interruption. To modify the status of linked cards visit open the cards in Azure DevOps and update its status. Thanks to the status mapping, that will be applied automatically on the story map as well according to your settings.
💡 Tip - Learn more about How to setup your custom workflow on StoriesOnBoard.
Import settings
You can enable/disable for editor's ability to import new cards from Azure DevOps.
Using the "Advanced import filter" makes it possible to visualize only a selected part of the Azure DevOps project on a story map by using queries. This will allow you to only import those issues to the story map which is matching to your query.
💡 Tip - Learn more about How to import issues from Azure DevOps using queries.
Card synchronization
When you link your story map to a project you can manage how you would like to synchronize your data.
StoriesOnBoard supports real-time and bidirectional sync for the following:
sync title changes
sync description changes
sync estimation changes (additional settings required)
Area Path / Release synchronization settings
Release synchronization makes it possible to sync StoriesOnBoard releases with Azure DevOps iterations. In Azure DevOps, users are allowed to make multi-level releases. In StoriesOnBoard there is only one release level. However, in the integration settings you can select which path/level you wish to push your StoriesOnBoard releases. In case of any changes happening on iteration level, that will also be synced.
Please note that if you change iterations in Azure DevOps, you must perform an import and sync changes on StoriesOnBoard to stay updated.
💡 Tip - Learn more about How to enable release synchronization.
Impersonation
Using impersonation will allow Azure DevOps to log changes made by individual users.
If you are not using the impersonation, then changes made by any user will be shown as the act of the person who setup the integration.
