ADD A NEW IDEA

Integrations

Showing 950

Add status filter to Github importer

The importer shows all repository issues, including closed issues. It also doesn't show what the issue status is, so we must click through them to find those we want to import. I suggest: adding a status filter, set it to show open issues only sho...
Alexey Zimarev 5 months ago in GitHub 0 Future consideration

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 about 2 years ago in Azure DevOps Services and Server 0 Future consideration

Ability to see more than the last 200 logs in Aha-Jira Integrations

Sometimes we need to investigate synchronisation errors between Aha! and Jira. We can find these errors long after an initial error might have happened. We might need to go back to the original error which may have happened months ago. The limitat...
Guest over 4 years ago in Jira 2 Future consideration

VSTS Requirement ToDo's

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

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 almost 5 years ago in GitHub 4 Future consideration

Link to Salesforce record through Aha

I understand it’s possible to link a Salesforce case, account, or opportunity to an Aha! Idea. It would be much more convenient to go the other way around so that you can link an Aha! Idea to Salesforce through Aha. That would prevent us from havi...
Guest over 6 years ago in Integrations 1 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

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 over 1 year ago in Azure DevOps Services and Server 2 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 about 9 years ago in Pivotal Tracker 2 Future consideration

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 about 9 years ago in Jira 8 Unlikely to implement