Avion Knowledge Base
avion.ioSign inSign up
  • 👋Introduction
  • 👉Getting started
    • What is Avion?
    • Define your product backbone
    • Scoping and prioritizing your product
    • Creating your release plan
    • Aligning the team
    • Integrating with backlog tools
  • Docs
    • 👏Core concepts
      • Projects
        • Project team
        • Migrating to projects
      • Organizations
        • Invite a member
        • Remove a member
        • Roles
        • Transfer ownership
        • Configure your path
        • Delete your organization
    • 🚀Story map
      • Story map anatomy
      • Journeys and steps
      • Stories
      • Releases
      • Attachments
      • Tags
      • Personas
      • Labels
      • Dependencies
      • Search and filter
      • Sharing
        • Restricted links
        • Public links
      • Workflow
      • Importing data
        • Import from Excel
          • XLSX import template
        • Import from StoriesOnBoard
      • Exporting data
        • Export to PDF
        • Export to image
        • Export to CSV
        • Export to Excel
      • Rich text editor
        • Keyboard shortcuts
        • Known limitations
      • Keyboard shortcuts
      • Tips
    • 🤝Integrations
      • Backlog tools
        • Set up an integration
          • Authentication
          • Project / board selection
          • Backbone syncing
          • Map story states
          • Additional syncing options
          • Importing data
        • Sync data
          • Pushing
          • Importing
          • Attachments
          • Deleting data
        • Configuration
        • Pause an integration
        • Re-authenticate
        • Remove an integration
        • Maintenance
          • Removing stale webhooks
        • FAQs and troubleshooting
        • Services
          • Jira Cloud
            • Features
            • Set up
            • Permissions required
            • Mapping options
              • Mapping fix versions
            • Epics ~ our thoughts
            • Additional data syncing
              • Mapping custom fields
                • Company-managed projects
                • Team-managed projects
            • Migrating to epic hierarchies
            • Import using JQL
            • FAQs and troubleshooting
              • Required fields
              • Verify webhooks
              • JQL import issues
              • Workflow issues
              • Ghost cards (cards with a dashed border)
              • Limitations
              • Jira Cloud or Jira Server
          • Jira Data Center (Server)
            • Features
            • Set up
              • Creating an application link
            • Permissions required
            • Mapping options
            • Additional data syncing
              • Mapping custom fields
            • Import using JQL
            • FAQs and troubleshooting
              • Required fields
              • Ghost cards (card with a dashed border)
              • Jira Cloud or Jira Server
              • JQL import issues
          • Azure DevOps
            • Features
            • Set up
            • Permissions required
            • Import using WIQL
            • FAQs and troubleshooting
              • Verify webhooks
              • No Azure DevOps accounts were found for your user
              • Problems communicating with Azure DevOps
              • Work items couldn't be imported
              • Show epics in Azure DevOps backlog
              • Import limits
          • Trello
            • Features
            • Set up
            • FAQs and troubleshooting
          • GitHub
            • Features
            • Set up
            • Permissions required
            • FAQs and troubleshooting
              • What types of GitHub Projects are supported?
          • Linear
            • Features
            • Set up
            • Permissions required
            • FAQs and troubleshooting
      • Notifications
        • Slack
          • Set up
          • Configure notification settings
          • Remove Slack
      • Design tools and media
        • Figma
        • Adobe XD
        • Axure
        • Framer X
        • Invision Web & Studio
        • YouTube & Vimeo
      • Embed Avion
        • Confluence
        • Confluence Server
        • Notion
        • Coda
    • 🔒Security
      • Single Sign-On (SSO)
        • Setup & Configure SSO
        • Azure AD
        • Google Workspace
        • Okta
        • OpenID Connect
      • Two-factor authentication (2FA)
    • ❓FAQs
      • Attachment file types
    • 💳Billing
      • Plans and pricing
      • Legacy plans
      • Free trials
      • Billing and payments
      • Change your plan
      • Cancel your plan
      • Refunds
      • Startup, student and educational discount
  • Story Mapping Guides
    • How To Story Map — A Simple Example
    • Advantages of Story Mapping
    • A Recommended Workflow
Powered by GitBook
On this page
  • Can I use non-standard required fields?
  • Do I need admin rights in Jira?
  • I can't see a mapped custom field in Jira
  • Epic name vs epic summary
  • Workflows in Jira
  • Issue type deleted
  1. Docs
  2. Integrations
  3. Backlog tools
  4. Services
  5. Jira Cloud

FAQs and troubleshooting

Answers to common questions and possible fixes for common troubleshooting queries, specific to our Jira Cloud integration.

Last updated 1 year ago

Can I use non-standard required fields?

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. .

Do I need admin rights in Jira?

As mentioned in the setup guide, Avion requires the authentication of a user with Jira Administrator and Project Administrator permissions. These must remain throughout the duration of the integration. 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. .

I can't see a mapped custom field in Jira

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. .

Epic name vs epic summary

In company-managed projects, Jira uses both the Epic Name field and the Summary fields for epics. It's worth understanding Avion's behaviour here, especially if you want fine-grained control over these two fields.

If you rename an element that is mapped to an epic in Avion (journey, step or release), both the Epic Name and Summary fields will update. If you update the Epic Name in Jira, this change will occur only in Jira and Avion will still reflect the Summary field.

This can be useful as the Epic Name field displays as a small tag on issues. You might want a shortened version of the epic's Summary that Avion does not need to know about. If you ever want both fields back in sync, just update Avion-side 🤙

Workflows in Jira

Issue type deleted

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. .

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 panel and refresh your issue types.

🤝
More info →
configuration
More info →
More info →
More info →