Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Search results: Integrations

Showing 29 of 489

Extend webhook triggers so they can fire on additional field updates

What is the challenge? Aha! webhooks can currently be triggered only by changes to a set of standard fields (name, description, status, assigned user, dates, etc.). Many teams rely heavily on tags, record links but changes to these fields cannot...
Justin Woods 20 days ago in Integrations 1 Future consideration

​Create separate roles/permissions allowing users be created to View Integration settings versus Edit/Setup Integrations

What is the challenge? Giving users the ability to View integration settings or Edit integration Mapping without having ability to Setup/Create new integrations What is the impact? What we have today is users get ALL or Nothing. Admins onl...
Guest 6 months ago in Integrations 0 Planning to implement

Support Additional MFA Providers

What is the challenge? Aha! currently supports Duo for two-factor authentication (2FA). However, many organizations standardize on other MFA providers such as Microsoft Authenticator, Okta Verify, or Google Authenticator. Relying solely on Duo c...
Dave Ball 16 days ago in Account settings / Integrations 0 Future consideration

Azure DevOps Integration - Sync dependencies at UserStories/Requirements level

What is the challenge? Currently, Aha integration with ADO syncs dependencies at Features level only. We need to also be able to sync the dependencies at Requirements/UserStories level.Including dependencies between Features and User Stories. What...
Guest over 1 year ago in Azure DevOps Services and Server 0 Future consideration
136 VOTE

Aha! + JIRA feature/story relationships (e.g. is blocked by, depends on) should match

If one feature depends on another, and you create that dependency in Aha!, it will not be reflected in JIRA currently. If Aha! and JIRA feature/story relationships were maintained back and forth, then we could create more realistic roadmaps and st...
Guest about 10 years ago in Jira 22 Shipped

Dependency record links available as part of the Azure DevOps integration

I understand you've created the dependency link in Aha! with Jira, it would be great to have this in ADO (Azure DevOps) too please
Ben Snapper over 5 years ago in Azure DevOps Services and Server  / Dependencies 11 Shipped

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 8 years ago in Dependencies / Jira 3 Future consideration

Allow the assigned to User to be sync'd with Jira

What is the challenge? When assigning features in Aha that are then sync'd to Jira - the assignee field cannot be set What is the impact? When development teams use Jira and Product teams use Aha, the feature becomes the common currency. T...
Manesh Patel 4 months ago in Jira 0 Already exists

Notify users that Rally projects may take a long time to load when creating an integration

What is the challenge? Experiencing a significant lag (5 minutes+) when setting up Rally integrations. During the project selection step, the page appears to hang because it is loading significant volumes of projects and related settings from Rall...
Dale Potter over 1 year ago in Rally 0 Shipped

Rally integration - Create and update dependency relationships between features as part of two-way integration

When a feature is sent to Rally, also create predecessor and successor links according to feature links which exist in Aha! Changes to predecessor and successor links in Rally should create or delete feature links in Aha!
Matt Case over 9 years ago in Dependencies / Rally 2 Future consideration