Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 946

Filter noise from Jira integration logs

The log file currently reports on Jira tickets that are out of scope for the integration (e.g., bugs, stories, tasks) as defined by the integration template. These log entries typically end with "No changes made in Aha!" If I'm trying to find the ...
Sandy Kobayashi over 1 year ago in Jira 0 Future consideration

Automatically update roll-up release name in integrations

Who would benefit? Teams using roll-up releases extensively. What impact would it make? Easily keeping everyone informed of launch details. How should it work? When the user updates the name of the roll-up release, it should be updated in any mapp...
Nico Arias-Gonzalez 8 months ago in Integrations / Jira 0 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 t...
David Vins almost 6 years ago in Jira 8 Future consideration

Add context with Slack integrations

What is the challenge? A Slack Messages used to add comments to aha records or create ideas, by default, does not have context around who sent the message, when, what slack channel What is the impact? Either the context around the message is lost,...
Michael Gogos 4 months ago in Slack 0 Future consideration

Fix field population in Aha/Jira integrations to only rely on email address or other specific data

Today when the Aha/Jira integration runs it looks up users in Jira based on email, then failing to find a match it checks first name, then last name. Jira returns results for these and Aha will select the first return. The problem is that if we ha...
Guest over 2 years ago in Jira 1 Future consideration

When an integration update comes from JIRA, it would be useful to see the "integration" completed the update in history instead of the callback user.

The callback user usually is not the one making the update in JIRA. It is almost 100% someone else on the technology side and not the product team. JIRA indicates that the integration updated the JIRA issue. It would be nice if Aha did the same.
Wen-Wen Lin about 6 years ago in Jira 5 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 over 6 years ago in Trello 0 Future consideration

Salesforce Integration: Allow customization of terminology

Currently we can rename the title of the Salesforce widget. We can also customize all the text within the Ideas portal in Aha. For us, we want to use this connection but we don't want to call them ideas, but rather e.g. Requirements. This is possi...
Guest almost 8 years ago in Salesforce 0 Future consideration

Configure AHA! to support GSuite - sheets, slides, docs, etc.

We are a company that uses GSuite, this would allow us to pull data into our collaborative space and manipulate reports to personalize further than what AHA! current allows. Currently the inability to use AHA with GSuite causes delays and setbacks...
Shawna Wilson about 4 years ago in Integrations 0 Future consideration

IFTTT Integration

While there's preliminary Zapier integration. IFTTT is a bit more accessible and flexible for most things.
Guest almost 10 years ago in Integrations 2 Unlikely to implement