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
  1. Docs
  2. Integrations
  3. Backlog tools
  4. Services
  5. Jira Cloud

Epics ~ our thoughts

Last updated 1 year ago

In both classic and next-gen projects, Avion offers you the choice of what you would like to map your Jira epics to. Traditionally you might see Jira epics as mapping directly to an Avion journey. But some people would prefer to map them to Avion steps.

Both are indeed possible with our integration, but we also offer a completely new approach that we think is going to change the way you see epics. We offer you the ability to map your Jira epics to Avion releases. This is our recommended approach, but it may require a slight change in the mindset of your team, depending on how you track epics currently.

To evaluate the choices, let's take a look at some descriptions of the elements involved.

Jira Epics

In Jira, epics are just issues. They can be shown on a kanban board and can even have a status. This allows them to be marked as β€œdone”.

Avion Journeys & Steps

In Avion, a journey is a description of a user journey. The step inside the journey is a step that a user could take to undertake the journey. As we see it, user journeys are ongoing; they are never β€œdone” in a software delivery sense. Sure, they will evolve over time, perhaps changing their name, order or purpose, but they are always present.

Avion Releases

In Avion a release is a selection of stories that should be grouped together based on the desired outcome to the user. A release’s stories could β€” and likely will β€” span across multiple user journeys and steps. A release can be β€œdone”. Once all stories are completed and delivered to a live environment, the release is done and dusted β€” share the achievement with stakeholders, archive it and move onto the next release.

As such, we feel that Jira epics make a perfect mapping match for Avion releases and we proudly offer you the ability to do this in our integration! As far as we know, this isn't possible with any other toolsets or integrations. We would love to know what you think about this β€” πŸ‘ or πŸ‘Ž?

Finally...

As a side note, we have noticed that Atlassian have even decided to display epics in a roadmap view in next-gen projects. So it would seem that they also are moving in this direction.

An update

We've recently also added the ability to map Avion stories to epics. More options to consider! You can never have too much choice. Check out the .

🀝
docs
Jira's next-gen project roadmap screen (these are epics)