Setup Walkthrough


Avion uses the highly secure OAuth 2 protocol to allow us to authenticate as you with Jira.
Before you dive in, please note that the user that you choose to authenticate with Jira must be a Jira Administrator as well as a Project Administrator. Avion will not let you proceed without these privileges. If these privileges are revoked after the integration is setup, you will get unexpected behaviour.
For this reason, you might choose to create a specific integration user that can be controlled by a trusted member of your business. This mitigates against the situation where you have to delete a user that Avion is authenticated with if a person leaves your business.
You might need to allow pop-ups if you browser blocks them, as Avion uses a pop-up window to authenticate with Jira.

Project Selection

Select the project you wish to integrate with. Currently Avion supports a direct mapping of one or many story maps to one Jira project, although we recommend keeping it simple with a one to one mapping.

Epic Mapping Choice

As explained earlier, here you can choose how you would like Avion to map to your Jira epics. It’s worth having a think about this decision, as it will change how the integration feels to work with on a day-to-day basis.

Story Type Selection

Select from all your issue types (not including your epic type or subtasks) and map one to Avion's stories.

Story State Selection

Map your Avion story states to any available Jira status. Don't worry, you can always update this again after setup.

Webhook Setup

Setting up a webhook means that every time a change is made in Jira, Avion is notified and can therefore update your story map. This is essential for a two-way integration.
Follow the prompts and Avion will automatically set up a webhook for you. If you already have webhooks for other story maps, please don't delete them. Each story map needs a unique webhook.

Importing From Jira

You can import your backlog from Jira and even specify a JQL query to restrict what issues are imported (although this is not a requirement).
In regard to your current epic to issue relationships:
    If you have a classic project, epic links will be respected on import
    If you have a next-gen project, parent/child epic links will not be respected, due to restrictions with the Jira Cloud APIs. We hope to be able to use this relationship in the future. Also, after import, next-gen projects use issue linking to represent epic hierarchy
Last modified 1yr ago