Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 924

Support AzureDevOps "work item deleted" events so my Aha records aren't out of date

Who would benefit? Anyone who manages an Aha board that syncs with Azure DevOps (ADO) What impact would it make? It would reduce out-of-date information in Aha & on roadmaps from records that rely on the ADO integration for updates. Additional...
David I. 5 months ago in Azure DevOps Services and Server 0 Future consideration

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, mast...
Guest over 5 years ago in Jira 5 Future consideration

Filter Slack notifications based on votes

What is the challenge? We get a large amount of posts every day that is too much for regular Slack integration. What is the impact? We don't use the Slack integration Describe your idea We'd like to only get Slack notifications when a post gets ab...
Guest about 2 months ago in Slack 0 Future consideration

Handle multiple FixVersions in JIRA

An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix v...
Danny Archer over 8 years ago in Jira 15 Future consideration

Keeping link to Jira when disable an integration

When we disable an integration to Jira, we mean it to be we have a new Jira project to integrate to. It makes it easier on the integration on the feature to not have a huge list of Jira projects to integrate to and only to the projects that are ac...
Carina Velazquez 10 months ago in Integrations 2 Future consideration

Provide alternative way to match users when email address is not exposed in Jira

Some time ago, Atlassian made changes that requires users to share their email addresses on an individual user profile setting. When that option is not checked, Aha! is not able to view their email address and if assigned user is mapped, is not ab...
Madeleine Black over 1 year ago in Jira 1 Future consideration

Support mapping Asset object fields through Jira integration

Who would benefit? Customers using the Asset object through Jira Service Management. What impact would it make? When these Asset fields are added to Jira issue screens, this would allow users to map these fields to Aha! fields through the Jira int...
Stephanie Lechner 6 months ago in Jira 0 Future consideration

Two-way integration with Redmine

Two-way integration with Redmine.
Chris Waters almost 9 years ago in Integrations 9 Future consideration

Allow for Lookup Fields to be mapped in SFDC integration

Who would benefit? Everyone What impact would it make? Allows for further data collection from SFDC in Aha! How should it work? Similar to how other SFDC fields are currently mapped in today's configuration.
Guest 4 months ago in Salesforce 0 Future consideration

Allow for parent-child linking across Jira projects without using an integration template

Some organizations that use SAFe store high-level records in one Jira project and the tactical work in team-specific Jira projects. These are often integrated to the same Aha! workspace. Today, you have to use the same integration template in the ...
Emily Yankush 11 months ago in Jira 0 Future consideration