Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 883 of 8597

Add Goal and Score to CSV Import for Master Feature and Feature

We are working integrations with some other systems, and the way part of it needs to be handled is via CSV file (Master Feature) - but Goal and Aha Score is not available for this import. This would be very helpful for our integration.
Amy Lackas about 5 years ago in Integrations 3 Future consideration

Trello Integration: Aha Release & Trello List

Add the option to have Aha create and update Trello Lists. When teams are using Trello for Project Management they typically need to have the Release and Trello list tied. The features become cards in Trello then they use something like Trello Hel...
Dan Pohlman almost 6 years ago in Trello 0 Future consideration

VSTS Requirement ToDo's

Can we get the VSTS Requirement To Do's transferring over as user story tasks?
Guest over 7 years ago in Azure DevOps Services and Server 3 Future consideration

Rally integration - Create and update dependency relationships between features as part of two-way integration

When a feature is sent to Rally, also create predecessor and successor links according to feature links which exist in Aha! Changes to predecessor and successor links in Rally should create or delete feature links in Aha!
Matt Case over 7 years ago in Rally 2 Future consideration

Map Aha! final score to JIRA priority

We manage the product through Aha! and the priority of features with Aha! Score. Product management can be easier and more efficient with an option to inform developers about priorities directly from Aha! to JIRA (We use JIRA Standard and Agile in...
Guest almost 9 years ago in Jira 9 Future consideration

Integration with Assembla

We use Assembla for issue tracking and Aha! for Roadmapping. Ideally the two products would be linked to tie roadmap features and milestones to Assembla.
Guest about 9 years ago in Wanted 13 Future consideration

Allow integrations such as Jira at the Product Line level

Integrations may be common across products within the same product line. It would save time and the possibility to make setup mistakes if these integrations can be setup one level higher
Steve C almost 2 years ago in Jira 0 Future consideration

Support the ability to change a Jira project key

Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.
Wayland Fox about 3 years ago in Jira 0 Future consideration

Gitlab - Connect Master Features to Epics, and more

As one more request to improve connection between Aha and Gitlab :) We need better integration between Master Feature, Features and Requirements of Aha to Epics and Issues of Gitlab. A sample could be Master Features -> Epics and Features/Requi...
Fabio Brito over 3 years ago in Integrations 3 Future consideration

Map JIRA Fix Version to Aha Release Phase

We would like to be able to map a JIRA fix version (and its dates) to an Aha Release phase Why? We like to plan in Aha using a monthly program increment primarily with features, similar to SAFe. But as a continuous delivery shop using Kanban key ...
David Vins over 5 years ago in Jira 8 Future consideration