Sync releases with epics in the JIRA integration

Like many other users, we map features to tasks and requirements as sub-tasks in our integration. For us it logically makes sense that JIRA Epics are therefore bound to releases (as tasks sit under Epics, and features sit under releases) - we use initiates as 'themes' that may have a number of releases added to them over time.

It doesn't appear as if this is supported in the Aha! JIRA integration, and when I create tasks within an epic in JIRA, and link them to 'features' in Aha! (telling Aha! to inherit all details from JIRA) for some reason it completely removes the task from the epic when I go back into JIRA and makes it an orphan task in JIRA, no longer associated to the epic it was originally created in.

  • Guest
  • Jul 25 2016
  • Shipped
Release time frame
  • Dec 14, 2017

    Admin Response

    We have launched an enhanced Jira integration. This integration will allow you to map Aha! releases to various issue types in Jira including epics, along with several other new capabilities including the ability to:

    • Set record mappings for Aha! initiatives, releases, master features, features, and requirements and link them to nearly any corresponding record type
    • Map default or custom fields in Aha! to any “like” field and specify which direction the updates should flow (e.g. from Aha! or from Jira)
    • Automatically send outgoing changes from Aha! or choose to review and approve them
    • Import records directly from Jira to make getting started in Aha! easy
    Check out the blog post for more details.
  • Attach files
  • Benjamin Moitié commented
    July 28, 2017 09:27

    any idea on the release date for this crucial feature?

  • Rob Parrish commented
    August 24, 2017 19:43

    This is an incredibly key feature to unblocking the organization scheme we'd like to use here. I'll just be manually creating & linking epics that correspond with Aha releases for now.

    Would appreciate an estimate on a release date.

  • Max Cascone commented
    October 16, 2017 16:42

    I agree; I've found that mapping Aha Releases to our Jira Epics is the best workflow for us (so far), adding Initiatives to that feels like just another layer of complexity that isn't needed. 

    Being able to choose to map Aha Releases with Jira Epics would be ideal. I would be open to renaming the terminology of Releases in Aha as Epics, as that would actually increase the commonality between the tools; I have a feeling the limitation is with the hierarchy design and not the terminology itself.