How to Use Avion's Azure DevOps Integration

📼 Watch our 90-second Azure DevOps integration example video →

What gets synced?

You have a variety of choices of what to sync. Currently we support syncing the following items:

Avion Item

Syncs To

Journey

Epic¹

Step

Feature¹

Story

User Story / PBI / Requirement / Issue

Lots of meta data from stories is also synced:

Avion Story Data

Maps To

Story titles

Title

Story descriptions

Description

Story sizes

Story Points, Effort or Size

Story acceptance criteria²

Acceptance Criteria or Impact Assessment

Story release information

Tag

¹ Syncing Journeys and Steps is optional. It is not supported if you use the "Basic" process in Azure DevOps.

² Syncing acceptance criteria is optional. It is not supported if you use the "Basic" process in Azure DevOps, as the field does not exist.

At what point do journeys and steps get synced?

If you selected "Don't sync journeys and steps" during the setup process, or you are using (or inheriting from) the "Basic" process template in Azure DevOps — journeys and steps will never be synced.

1. After the initial setup process import

When you set up an integration with Azure DevOps from Avion, you will be given the choice to import data from Azure DevOps. At this point, all of your epics and features that are in Azure DevOps will be created as journeys and steps in Avion. Any journeys and steps that were already in your story map in Avion will also be created and synced in Azure DevOps.

2. As you create new journeys and steps in Avion

If you add more journeys and steps in Avion, these will be immediately created and synced with Azure DevOps.

3. When you run the re-importer from Avion

If you add epics and features in Azure DevOps, these will not be created and synced in Avion, until you use the re-importer. Once epics and features are re-imported, they will be created and synced in Avion as if they had been created in Avion. How to re-import →

Once a journey or step is synced, any further changes, such as title or structure will remain in-sync in the background.

At what point do stories get synced?

1. After the initial setup process import

When you set up an integration with Azure DevOps from Avion, you will be given the choice to import data from Azure DevOps. At this point, all of your User Stories / PBIs / Requirements / Issues that are in Azure DevOps will be created as stories in Avion.

2. After you push a story or a release from Avion

Unlike journeys and steps, stories are not created and synced straight after they are created in Avion. You will need to push them to Azure DevOps. You can push individual stories and you can also push any release (which will push all stories in the release) that isn't Unplanned.

3. When you run the re-importer from Avion

If you add User Stories / PBIs / Requirements / Issues in Azure DevOps, these will not be created and synced in Avion, until you use the re-importer. Once re-imported, they will be created and synced in Avion as if they had been created in Avion and pushed as part of a release. How to re-import →

Once a story is synced, any further changes, such as title, description, size, A/Cs, parent structure or release will remain in-sync in the background.