We have removed the restriction on integrating a single story map to a single area path in Azure DevOps! 💥. You can actually now integrate multiple story maps to a single project in Azure DevOps and all story maps will stay in sync with each other and ADO! I bet you've never heard of three-way (or more) sync before?!
We are also planning to improve the area path support in the future to help you evolve your map with your ADO projects. More on that in the coming weeks.
Finally, we've also loosened a few role restrictions — story map collaborators that aren't team admins (or the story map creator) can now re-import items from ADO, Jira and GitHub. They can also rename the default story labels.
Duplicate stories 👊
You can now duplicate a story by right-clicking on it and selecting "Duplicate story". This will copy the name, description, size, state and personas of that story and make a duplicate right below it. Simple!
GitHub integration 👩💻
We are proud to announce that we now integrate fully with GitHub! We are leveraging GitHub's project boards to create an in-depth integrated experience that enables you to sync your story titles, descriptions, sizes, states and releases!
If you use a repo-based project, we use GitHub's milestones to integrate tightly with your Avion releases. You can also use organisation-based projects to sync up with Avion (but be aware that we don't sync up releases for these).
Avion uses issues and project cards to sync all your story data
For a more comprehensive understanding of how our integration works, check out the GitHub setup guides →
Fixed an issue where story statuses were not being synced when they were changed in Avion
Fixed an issue where Jira cloud re-imports were failing under certain scenarios