Comment on page
FAQs and troubleshooting
Answers to common questions and possible fixes for common troubleshooting queries, specific to our Jira Data Center integration.
You may see unexpected behaviour if you add required fields to your issue types being used by Avion. Please stick to the defaults for required fields. More info →.
A common problem we hear is that a field is not visible on an issue.
For example – a custom field value mapped to the backbone, story sizes or even epic links. Jira can be a little tough to manage, but ultimately, you will need to seek out your issue type's "screen" configuration and add the field. More info →.
If you use complex workflow options in Jira — such as — restricting an issue's next status depending on the issue's current status, you will need to abide by these rules when changing story states in Avion. If you don't, you may miss changes or ultimately end up out of sync. Read more.
If you are using a project that is not rooted in agile — i.e: not a Scrum or Kanban project in Jira, you are not able to use the Story Points field. Therefore, this will not be available to map to Avion's sizes.
File attachments must be enabled on your instance before trying to sync attachments from Avion. You may need a Jira Data Center administrator to help you with this. We recommend you follow Atlassian's documentation to configure this correctly.
If an issue type has been selected to push to from Avion and is subsequently deleted in Jira, you will receive an error during pushing. To fix this, head to the configuration panel and refresh your issue types.
If you are unable to get Avion to recognise your Jira instance, you may be running Jira behind a firewall or a VPN may be required to connect to your internal networks to successfully connect to Jira.
If you think this is the case, please don't hesitate to get in touch with via email at [email protected], so we can assist.
Last modified 3mo ago