Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 947

Add 2-way integration mapping for release start and end dates

Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release. Now that this date is set manually, it should be poss...
Austin Merritt over 4 years ago in Azure DevOps Services and Server  / Integrations / Jira / Rally 3 Planning to implement

Complete Auto Import Functionality -- not just children of existing linked records

This is regarding the JIRA integration feature: Automatically Import New Records: Records will be imported automatically to Aha! from Jira. This applies to records which are created as children of previously linked initiatives, releases, master...
Guest over 5 years ago in Jira 5 Future consideration

Rally Project name change should be reflecting in the Aha! Integration

What is the challenge? Rally Project name is updated but the project name is not updating in the Aha Integration Project Tab? What is the impact? Users see the wrong project name in the Aha integration and think they need to create a new integrati...
Mike Jacobson 6 months ago in Rally 1 Already exists

Ability to send Aha Defects to Rally as Rally (CA Agile) Defects

We need the ability to send defects to Rally. Currently, we are only able to send features/ user stories which cannot be converted to defects once they are in Rally.
Guest about 7 years ago in Rally 2 Future consideration

Add Salesforce integration to Salesforce custom objects.

We use custom objects in our Salesforce org to track things like feature requests, bugs and other system support related issues. Allowing us to integrate Aha to a custom object would allow us to use the Aha integration with our existing org struct...
Guest over 9 years ago in Salesforce 3 Future consideration

Add ability to map Custom Aha! Tables to Jira

Add the ability to map custom fields from custom tables in Aha! to Jira.
Guest over 7 years ago in Jira 5 Future consideration

Integration with WorkBoard

Our company is looking to adopt WorkBoard as our corporate standard for OKRs. Our development business units use Aha to manage our product strategy and roadmaps so we need to have integration between the 2 systems in order to maintain continuity o...
Joe Granville almost 4 years ago in Wanted 3 Future consideration

Lucid Charts Integration

I use Lucid Charts currently and would like to be able to integrate them into my requirements flow.
Guest about 6 years ago in Wanted 9 Future consideration

Integrations 2.0: Add dependency link to connect records without natural relationships together

In integrations 1.0 if I mapped Features = Story Requirement = Task Aha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other. ...
Danny Archer almost 7 years ago in Dependencies / Jira 3 Future consideration

Integration with ToDoist

It would be very useful to have an integration with ToDoist, so that all To Does assigned to me be automatically added in a specific project in ToDoist. A new trigger for Zapier like "New to do assigned to me" might work too.
Guest almost 10 years ago in Wanted 10 Unlikely to implement