Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 59

Deleting a feature or requirement should delete the linked Jira issue(s)

When I delete a feature or a requirement in Aha!, I then have to go to Jira and delete the corresponding epic or story. Would love it if deleting a feature in Aha! deleted the linked epic in Jira and all stories for that epic. Likewise, deleting a...
Guest over 10 years ago in Jira 11 Will not implement

If a comment is deleted in Jira, please delete that comment in Aha! also

Some comments are for testing purposes or are not correct. If we have decided to delete a comment from an epic or story in Jira, we would like it to be removed from the feature in Aha! as well.
Kelly Sebes almost 7 years ago in Jira 1 Will not implement

Pivotal Tracker Integration Mapping

It would be helpful if one of the mapping options with Pivotal Tracker could include the following options: Master Feature to Epic Feature to Story Requirement to Task Instead, the only option for mapping to Epics in PT is to use Initiatives. Th...
Tom Beck over 6 years ago in Pivotal Tracker 1 Will not implement

More complete field mapping between Aha! and FogBugz

Both products are feature rich and have many alignments which would be great to keep in sync. Aha! Feature Type - FogBugz Case Category FogBugz has an "Area" concept which doesn't map directly. At least being able to select the target area for ne...
Guest over 9 years ago in Integrations 4 Will not implement

Add Actionable Agile into your dev product

Who would benefit? anyone using Kanban and want's accurate process measurements What impact would it make? Better insights into the flow of work in your system, better forecasting of future work without having to ever ask for estimates that are mo...
Mike Lowery about 1 year ago in Wanted 0 Will not implement

Integrations 2.0: JIRA Default map Aha! URL to JIRA Aha! Reference field

1.0 did this; 2.0 does not. As a user I have to manually add the mapping between the URL field for an Aha! record and the Aha! Reference field for the JIRA record. For Releases we automatically map the URL to the description field. For Features/...
Danny Archer over 7 years ago in Integrations 0 Will not implement

Ability to manually link features in Aha to existing Redmine items

As a Redmine user with many projects in flight, I want the ability to link a feature in Aha! with an existing Redmine feature so that I can manually create an integration between the two objects.
Nathaniel Collum over 7 years ago in Integrations 0 Will not implement

Two-way integration with Bugzilla

Two-way integration with Bugzilla
Chris Waters over 9 years ago in Integrations 4 Will not implement

Salesforce Report with Opportunities and Ideas

Currently Salesforce reports for ideas only pull ideas. Our sales team asked for a SF report with Ideas and Opportunities so they are able to report on the value of their ideas. Sales people live in SF so this would help to live there and not just...
Guest almost 10 years ago in Salesforce 3 Will not implement

Comments entered in Aha are not being pushed to Redmine

Currently, Aha/Redmine integration - comments entered in Aha are not pushed to Redmine. It would be more user friendly if this info could be pushed to Redmine . So that user does not need to duplicate their work in both Aha and redmine to re-enter...
Guest over 7 years ago in Integrations 0 Will not implement