Skip to Main Content

Share your product feedback

Status Already exists
Categories Features
Created by Cindy Datlof
Created on May 1, 2020

Allow for Features to Integrate with Multiple Epics

We have multiple teams working on multiple Epics in JIRA that all track to a single Feature. It would be very helpful to enable integration of a Feature to multiple JIRA items.

  • Attach files
  • Jennifer Briden
    Reply
    |
    Feb 10, 2022

    I have enabled epics in Aha and group features into epics there. To reduce confusion for our teams, we've renamed Aha epics to "roadmap items." For mapping, the roadmap item maps to an Initiative type in Jira and the features in the roadmap item are linked as individual epics in Jira.

    Aha

    Jira

    Roadmap item (epic)

    Initiative

    Feature

    Epic

    Feature

    Epic


  • Venk Nallapati
    Reply
    |
    May 14, 2020

    Hello there,

    Yes a single feature in Aha is being tracked by multiple epics in JIRA. We have this feature broken down into different epics: Infrastructure, Licensing, Development, Security, Validation. While we do have several cross dependencies that we want to track on other JIRA boards, in the long run, we want to organize our implementation into several EPICS.

    Hope this gives you some insight into what we are trying to achieve.

    Kindly advise if this option does currently exist?

    Many thanks,

    Venk

  • Admin
    Austin Merritt
    Reply
    |
    May 7, 2020

    I am going to mark this as already exists for now given the explanation above. I can update the status if this is not accurate based on your use case. Let me know if you have additional details that you can share. Thank you!

  • Admin
    Austin Merritt
    Reply
    |
    May 1, 2020

    Hi there, thank you for your idea! I am curious about your use case. Are the various teams working in different Jira projects? Are there duplicate issues in Jira or are these truly different issues?

    If they are truly different issues, one idea would be to break these out into separate features in Aha! that all map to a single master feature. Could that work for your use case?