Setup your Jira integration in Avion
Our in-depth, but straightforward setup process will guide you through all the different syncing possibilities, so you can dial it in just how your team likes it.
Jira is such a powerful backlog management tool, it's no wonder so many companies use it to help them manage their software development sprints. However — it sorely misses a user story map view — enter Avion.
Support for classic and next-gen projects
Avion accommodates both classic and next-gen projects, meaning that you can sync Jira with an Avion story map no matter what your chosen project type is.
Three ways to sync your epics
Avion provides you with multiple options for how you would like to sync the structure of your user story map. As well as being able to use Jira’s custom fields to display additional data from Avion, you can sync Jira epics in three different ways:
Don't want to sync epics?
You can also integrate with Jira without syncing the structure and hierarchy of your story map — keeping your Avion stories and Jira issues in sync — without touching your epics. This lightweight approach allows your dev team to organise their backlog however they want.
Check out the Avion docs for more information on the syncing options
Automatic two-way syncing, always
Whenever a release or user story is pushed from Avion to Jira, all data will be kept in sync whichever tool is used to update it. So you can update your titles, descriptions, story sizes or structure, safely in the knowledge that both tools are up-to-date.
Sync with Jira fix versions / releases
If you don't choose to sync your Avion releases to Jira epics, you can alternatively use Jira's fix versions. Your fix version's progress will stay in sync with the running states of the user stories in that release.
Plan in Avion. Execute in Jira.
Don’t confuse your dev team by trying to plan upcoming releases where day-to-day work is tracked. With Avion, you can freely plan your product releases, safe in the knowledge that you aren’t cluttering your Jira backlog. This means you can keep your dev team focussed on what needs to happen right now whilst retaining your longer-term product roadmap in Avion.
How does it work?
Import existing data from Jira
Import all your current project’s user stories into Avion, so you can start linking them up with your user journeys and steps. These stories will be immediately two-way synced.
Push new stories and releases
Define and prioritise new releases within Avion and then push them to Jira, where your dev team can start picking up the work.
Track and monitor in either tool
Any card that is synced will remain up-to-date in either tool automatically, so you can monitor your dev team’s Jira updates right from your Avion user story map.
Evolve your processes
Use our Jira configuration options to tweak and update how Jira statuses are mapped to your Avion workflow.
