Comment on page
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. More info.
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.
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.
Select from all your issue types (not including your epic type or subtasks) and map one to Avion's stories.
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.
Your JQL query will be saved for future imports, but can also be changed later
Last modified 1yr ago