Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 988 of 9718

Integration to Azure DevOps for teams capacity planning

We would like to use Points based capacity planning but it needs to be integrated with (in our case) Azure DevOps which is where the team is committed to and working on work. All of our Features and Master Features (Epics) in Aha are calculated ba...
Heath McCarthy about 5 years ago in Azure DevOps Services and Server 2 Future consideration

Inherit the hierarchy of the area paths from Azure Dev Ops

When integrating with Azure Dev Ops, the area paths should inherit the same hierarchy when represented in Aha. For example, hierarchy in Dev Ops could be: Company/ Company /Functional Area Company/Functional Area/Team The Aha Azure devops integrat...
John M about 5 years ago in Azure DevOps Services and Server 5 Future consideration

Sync owner field from Aha! to Pivotal Tracker

Synchronisation of the owner field. Stories created in Pivotal Tracker should have the corresponding owner on the Pivotal Tracker side. That can be determined based on e-mail, your team confirmed that it is possible. Priority 2 of 4
Guest about 11 years ago in Pivotal Tracker 2 Will not implement

Ability to map constants to custom fields in Github

Who would benefit? Anyone with a Github integration What impact would it make? Right now, the only way to prevent unhandled errors is to research the backend technical ID's and map those as constant values to send choice values over as a constant ...
Stephanie Lechner almost 2 years ago in GitHub 1 Likely to implement

Sync Aha! To-dos with Google Tasks

What is the challenge? I work in a G suite company where all my work funnels those tools. What is the impact? I do not check or follow-up on Aha! to-dos because I don't have regular visibility. Describe your idea Allow a two-way integration betwee...
Guest 8 months ago in Wanted 0 Future consideration

Allow requirements to be associated with the release record

The Problem: Jira requires each User Story type to have a Fix Version associated with it, similar to the Epic. The Epic will have Stories with various Fix Version ( the User Stories don’t inherit the Epic Fix Version as story releases are weekly o...
Guest about 6 years ago in Jira 0 Future consideration

Show name of user whose token is being used in ADO integration

Who would benefit? Admins of accounts with ADO integrations What impact would it make? When an ADO integration is created, a user with the correct permissions must enter their token to authenticate the integration. However, the token owner's name ...
Bonnie Trei about 2 years ago in Azure DevOps Services and Server 0 Future consideration

When an Idea is Promoted to a Feature, Automatically Copy Idea's *Subscribers* (as well as Watchers) to the Feature. And, Sync the Watchers & Subscribers to JIRA

Hi All, We are having some trouble keeping an idea's subscribers & watchers in the loop on the idea ticket from its conception through completion. The fact that people can subscribe & watch ideas is great (we find the email updates very he...
Guest over 9 years ago in Ideas / Jira 4 Unlikely to implement

Deleting a feature or requirement should delete the linked Jira issue(s)

When I delete a feature or a requirement in Aha!, I then have to go to Jira and delete the corresponding epic or story. Would love it if deleting a feature in Aha! deleted the linked epic in Jira and all stories for that epic. Likewise, deleting a...
Guest about 11 years ago in Jira 11 Will not implement

Update the Feature % Complete field based on User Stories of the DevOps Feature

Update the Feature % Complete field based on User Stories of the DevOps Feature that is linked to the Aha Feature. The Software Product Plan does just that! In DevOps, this information is a calculated field, which can be easily configured in Board...
Guest almost 3 years ago in Azure DevOps Services and Server 2 Future consideration