Avion uses the highly secure OAuth 1 protocol to allow us to authenticate as you with Jira.
Assuming that you have already created an application link with an administrator, the user that you authenticate with will just need access to the specific project that you want to integrate with.
You might need to allow pop-ups if you browser blocks them, as Avion uses a pop-up window to authenticate with Jira.
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
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.
If you want more details about epic mapping, you can read our guidance for Jira Cloud here (all the same principals apply to Jira Server): A note on epics.
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.
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
Here 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).