RELATED IDEAS
JIRA Import multiple issue types as requirements mapped to parent feature
As a PO, I’d like to import multiple issue types (i.e. bug, story) as requirements that map to their parent features so that existing Jira Projects can be imported into Aha! Products in a single import
| Release time frame | 1 month |
-
ADMIN RESPONSEAug 22, 2018
Now you can map record types in Aha!, including requirements, to multiple records types in your dev system.
See how to configure this new integration capability.
2
MERGED
Automatically add JIRA stories linked under JIRA epics as requirements in Aha!
As a user of JIRA and Aha!, when I create an epic in JIRA with stories, design stories and tech stories linked to that epic, I want to be able to have all of those stories link back to the Aha item as a requirements line item so there is more visi...
0
Shipped
13
MERGED
Import from Jira: Ability to use more than one issue type for requirements
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 i...
2
Shipped
© 2024 Aha! Labs Inc.•All rights reserved
Are there any news?
Having issues bringing in tasks and research items into Aha! from Jira. multiple issue types would be a huge improvement.
Any updates on this Aha? This is still a want from customers. As of right now, I have to mass change swaths of tickets to the specified ticket type, reimport, then somehow remember what each issue type was before the change.
I agree! This would be very helpful when syncing with JIRA. I currently import into Aha! all bugs from Jira and dump those into a monthly release in Aha! This works fine without the issue type, but when I want to then do any filtering across releases or filter features by type, I'm stuck unless I went in and manually changed each issue type.