Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit APP-I-1048 JIRA Import multiple issue types as requirements mapped to parent feature.

Import from Jira: Ability to use more than one issue type for requirements Merged

Import from Jira: Ability to use more than one issue type for requirements would be useful because we often have Jira Epics mapped to Aha! Features and those Epics have many different types of requirements that we would like to show dependencies in the Portfolio view.

  • Barb O'Connell
  • Feb 4 2015
  • Shipped
Release time frame
  • Guest commented
    February 05, 2015 06:05

    Many of our traditional engineering projects in JIRA use only user stories with epics, but our Operations projects uses multiple jira issuetypes for requirements - tasks, tickets, maintenance tickets.

    We see the value in using Aha! for long-range planning for Operations, in addition to our more traditional engineering groups.

  • Guest commented
    June 17, 2015 22:41

    Aha should not restrict the issue type you can use to link, especially as this isn't the behavior on import. I can import any issue type as a feature and it will load. I could not do the same with a link.