Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 944

VSTS Requirement ToDo's

Can we get the VSTS Requirement To Do's transferring over as user story tasks?
Guest about 8 years ago in Azure DevOps Services and Server 3 Will not implement

Ability to cancel background jobs

Who would benefit? all teams and aha What impact would it make? It would allow admins to stop a job from running such as an import when it is realized an integration was set up wrong etc. This will benefit aha because it will prevent unnecessary p...
Guest 10 months ago in Integrations 1 Future consideration

Support linking the Aha! URL field to the Azure DevOps Hyperlink field

Goal: We want to see in DevOps which Item it syncs with in Aha! Current set up: Aha! URL field linked to Hyperlink field in DevOps Challenge: We are using the hyperlink field to capture URLs to multiple sources. This is all being done in a single ...
Euan Callow over 3 years ago in Azure DevOps Services and Server 2 Future consideration

Allow for mapping to-dos in Asana integration

In some cases, Asana sub-tasks are more closely related to Aha! to-dos than requirements. For example, a feature may have to-dos related to marketing tasks which need to sync with Asana. An option to map To-dos to Tasks or Subtask would provide a ...
Austin Merritt over 6 years ago in Asana / Integrations 4 Future consideration

Synch story point estimates between Zenhub and Aha Epics (features)

We have linked Epics (Features) in Aha with Epics in Github Enterprise, and that is working fine. however we are using Zenhub to create story point estimates within Github, and would like to be able to reflect those estimates in Aha so we can do c...
Guest about 5 years ago in GitHub 4 Future consideration

Including Dependencies in Jira integration at requirements/story level

We have been really enjoying the newer ability to include dependencies for features in our Aha-Jira integration, but are running into the issue not getting the same level of transparency for the user stories - to combat this, we would like the abi...
Trey S about 3 years ago in Jira 0 Future consideration

Tags should propagate bidirectionally into Pivotal Tracker

Much like status, it would be nice if tags on features would propagate instantly to stories in PT bidirectionally. We have historically used PT labels to organize aspects of our sprint. It would be nice to setup initial tags in Aha and have those ...
Jason Novek over 9 years ago in Pivotal Tracker 2 Will not implement

Support mapping JIRA Tempo Account field

When using the JIRA Tempo plugin to track work time, it is useful to link issues to Accounts - for this the plugin exposes a custom field named Account. This field, formerly called Billing Key, is used among others in reporting, to decide which cu...
Guest over 9 years ago in Jira 8 Unlikely to implement

Expose scorecard metrics as integration fields

Currently, scorecard metrics do not appear to be available to integrations. We would like to represent these components in our development system in the interest of transparency to our development teams, but there is no way to get this data across...
Bob K over 5 years ago in Integrations 3 Future consideration

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