Skip to Main Content

Share your product feedback

ADD A NEW IDEA

My votes: Integrations

Showing 947 of 9056

Aha! and Slack Integration

With a digital first mindset on the rise and more tools like Slack being used for asynchronous communications and collaboration, the ability to create workflows from within Slack to be able to submit an Idea or create an epic or feature would impr...
Karie Kelly over 3 years ago in Slack 0 Already exists

Provide the ability to map the Release field from a Feature or Epic to an external system such as ADO

Given that AHA is all about releases and ADO is all about time lines, the concept of a Release in AHA is quite different than what exist in ADO - yet there is a Target Release field in ADO as well as in the Feature of AHA - please can this be expo...
Dirk K over 3 years ago in Azure DevOps Services and Server 1 Future consideration

Only update Jira FixVersion if the Release has actually changed in Aha and the Jira FixVersion has not been edited

In my process I want Aha to be my master in terms of planning, but allow Jira to update details as actual releases are made. By this I mean that I will plan a release such as "Q4 2017" in Aha and push to Jira. As work is completed in Jira the issu...
Kevin Burges about 7 years ago in Jira 0 Unlikely to implement

Calculate Epic Completion Based on JIRA Epic Completion

The options to calculate the completion of an epic in Aha is only based on user stories, but there are other items in JIRA that determine how complete an epic is. It would be helpful to have the progress bar completion automatically reflect whatev...
Rachelle S almost 2 years ago in Jira 0 Already exists

Advanced Integration with Zapier

I was trying to do an integration between Freshdesk and Aha, and since there is no direct integration, I used Zapier, however, the fields available at Zapier are just the idea title and description, all the custom fields I have on Aha's ideas are ...
Guest over 3 years ago in Integrations 0 Future consideration

Sync Sprints betweeen Aha! and Rally

As product owners use Aha as the primary repository to develop and track their roadmap, they want to enhance their planning phase by improving the existing configuration between Aha and Rally. Currently, capabilities, features, and user stories ar...
Guest over 3 years ago in Rally 0 Future consideration

improved metadata rest services for fields

For users trying to interface with the Aha service via the rest services there is a definite lack of available services for fields. There needs to be a way to validate fields being sent to Aha. Currently there are only services that return filed d...
Tim McCaskill over 5 years ago in Integrations 1 Future consideration

Assignee of feature in Aha! should propagate to Gitlab

As a user of Aha! / Gitlab integration, I would like to assign a feature in Aha to a specific user and have it show up as assigned to them in Gitlab, so that they are aware of the new feature and can take responsibility to break it down further in...
Guest over 7 years ago in Integrations 0 Future consideration

Provide JIRA (and other) Integration Information in Account Backup

The account backup dump doesn't include any information about integrations and their related field values, features and master features.
Micah Mayo over 7 years ago in Integrations 1 Will not implement

Salesforce integration without permission set

Currently, the Salesforce / Aha.io integration requires using a permission set. A System Administrator must assign individual users in Salesforce to this permission set, in order for them to use the Aha.io ideas portal. That's a fine approach, but...
Angus Davis about 9 years ago in Salesforce 1 Unlikely to implement