We would like the ability to have new records created in JIRA/Rally automatically import into Aha!
Currently, they have to be accepted in Aha! prior to import. This causes an extra step in our workflow we do not wish to have to go through each time.
Danny Archer
over 7 years ago
in Integrations
7
Shipped
Link existing GitHub issues with a new Aha! Feature
The current Aha! - GitHub integration lets you sync features to GitHub issues. This won't work in the opposite way. However, It'd be nice to have an editable field to reflect that the Aha! feature is linked to a GitHub issue.
We often use various lists and reports. Unfortunately, their utility is limited due to the fact that filters are only inclusive. We'd like to see filters built with the ability to exclude certain things (i.e. tags, keywords, dates, etc)
Customised text formatting for sharing roadmaps (or at least larger font sizing).
Very happy with the web presentation of roadmaps in notebooks, however we still need to print them effectively in some circumstances. Also would be valuable to be able to fit to one page. The ability to change text size when exporting to a specifi...
Aha Develop: Expose Prioritized Backlog status in record properties
We use the Prioritized Backlog as part of our workflow in Aha Develop, records going from parking lots ("Engineering Work") or Roadmaps ("Product Work") into the Prioritized Backlog as they are refined and become ready.It would be really helpful i...
Map Jira's "Won't Fix" resolution status to Aha!s "Won't implement" status
When the Jira workflow is set up to "Close" a ticket with the resolution status of "won't fix," there currently is now way to map that against the Aha workflow.
It would be great to also access the Resolution status from Jira to handle this case.
It would be very useful to bulk edit requirement fields including:
Requirement assignment
Requirement logged effort
Requirement status
Requirement original estimate
Requirement logged time
It would be helpful if we had the ability to copy a requirement to the same feature. We use requirements as product backlog items. Sometimes they are too big. It would be useful to be able to copy a requirement as the first step in splitting it.