Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 946

Ability to configure integrations not to create new records in Aha

In the 1.0 integrations I had configured it to not try to create new Aha! records when records were created in JIRA. I would like to be able to do the same in the 2.0 integrations. Currently when someone creates a new issue in JIRA I see this appe...
Kevin Burges over 6 years ago in Jira 0 Future consideration

Support epics with integration webhooks

Currently, integration webhooks are only available for Features and Releases. I would like to be able to integrate epics with integration webhooks so I can send epics to zapier, my own integrations, etc. At least enabling me to sidestep the poor s...
Nir Soffer over 3 years ago in Integrations 0 Future consideration

Integration with Zoho Projects

Once the product roadmap is ready, it needs to be transferred to Zoho Project management platform (https://www.zoho.com/projects/) for product development.
Guest over 3 years ago in Integrations 0 Future consideration

Integration between Aha! and Jira Align (formerly Agilecraft)

Jira Align is a requirements tracking platform that was formerly Agilecraft, and is fully integrated with Jira. Our teams that are using both Jira and Jira Align are mapping their Epics in Jira to parent Epics in Jira Align, so that the roll-up pr...
Adam Zoghlin over 3 years ago in Integrations 1 Future consideration

Add Boolean Field mapping for Rally 2.0 Integration

Currently, there is no way to map Boolean fields in Rally to Predefined Choice fields in Aha. A Boolean field in Rally can only be mapped to a text field or a few other options like Aha Rank, and can only bring the data from Rally to Aha, not the ...
Stephen McAdams about 2 years ago in Rally 0 Future consideration

Allow mapping Release as a field on Requirements in Azure DevOps integration

Due to our iterations setup in Azure DevOps (ADO) we do not currently map Releases as a record. We are sending this instead as a field on the Epic and Feature records to a custom field in ADO. We would like to do the same on Requirements but it is...
Guest over 3 years ago in Azure DevOps Services and Server 0 Future consideration

better redmine integration - requirements are children of features, and tasks are children of requirements

redmine integration is very helpful and needed. "When a feature is copied to Redmine one issue will be created for the feature. If the feature has requirements then each requirement will also be sent as an issue." there should be a way of re...
Michael Martini almost 9 years ago in Integrations 0 Unlikely to implement

Calculated mapping of number fields in integration with Jira

We would like to specify a conversion factor or formula to map numeric fields between Jira and Aha! numeric fields, especially a Jira number field and Aha!'s Original Estimate field. This would allow us to enter hours into a Jira number field whic...
Jor Bratko about 2 years ago in Jira 0 Future consideration

Show JIRA # rather than Aha # on Roadmaps

JIRA came first at our company, and only a handful of users use Aha -- consequently, when I publish a roadmap, it is assumed that the issue numbers shown on the roadmap are JIRA issue numbers -- this creates a lot of confusion. I would like to be ...
Cameron O'Rourke almost 9 years ago in Jira 2 Unlikely to implement

Integrate Gliffy to enable editable flow diagrams in notes

I currently have to create flow diagrams outside of Aha and paste in a static version that others can not change. This is very restrictive and does not follow the collaborative flow I like to use. https://www.gliffy.com/
Guest almost 9 years ago in Wanted 3 Unlikely to implement