Integrations

Showing 945

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

22 VOTE

Have users in Jira and Aha matched for comments, updates etc

I realise this is not Aha's fault, but if we put the issue here with more info, users will be more likely to go to Jira to vote for the issue there. Currently whenever someone comments on an issue in Jira, in appears in Aha as a comment from the p...

Guest about 10 years ago in Comments / Notifications / Jira 1 Unlikely to implement

13 VOTE

Auto Resend all Fields per release

Right now, even after we manually click "Send to JIRA" for the first time for a release, subsequent changes to that release ( for eg. Addition of a feature under that release) do not automatically go through to JIRA. We'd want to have all changes ...

Guest almost 6 years ago in Jira 2 Future consideration

3 VOTE

Notification when an integration is down

Would like to see some way of setting user(s) to be notified if there is an interruption in communication between integrated system.

Guest over 1 year ago in Jira 1 Future consideration

14 VOTE

Integration with JAMA

As a product Manager, I Manage requirements through JAMA, I want to align Aha! with JAMA so feature requirements are aligned accross tools.

Guest over 6 years ago in Integrations 5 Unlikely to implement

15 VOTE

Develop Aha! triggers for Microsoft flow

Microsoft flow has over 175 triggers currently available. Examples include Zendesk - When an Item is created, Wunderlist - When a New task is created, Saleforce - When a record is created, Pivotal Tracker - When a story is created, etc. Having acc...

Guest almost 7 years ago in Integrations 0 Future consideration

5 VOTE

New features created via an ADO integration are assigned to the parent epic release by default

Key problem: the "Parent" field in ADO can contain only one value. In ADO, a feature is automatically associated to the same theme as its' parent epic, but in Aha! this is not the case. So when features import, we associate them with the correct p...

Bryan McElhinney over 2 years ago in Azure DevOps Services and Server 0 Future consideration

16 VOTE

Ability to create JIRA integration thorough Aha API

We have teams with several projects and creating it through templates is not practically scalable, hence require an API to create JIRA integration manually

Guest over 7 years ago in Jira 3 Future consideration

17 VOTE

Integration with VersionOne

Bi-lateral sync with VersionOne

Guest almost 8 years ago in Integrations 0 Unlikely to implement

13 VOTE

Support filtering in the API

The API pages the data it returns, and the pages are limited to a maximum of 200 records. In scenarios where it isn't possible to programmatically iterate through the pages, such as reporting & (Power)BI, it would be incredibly useful to be ab...

Daniel McGrath about 6 years ago in Integrations 1 Future consideration

Share your product feedback

Please enter your email address

FILTER BY CATEGORY