ADD A NEW IDEA

Integrations

Showing 945

Allow To-Do's to be mapped to JIRA Issue Types

We would like to be able to make better use of Aha To-Do's so that they carry over to our JIRA Agile installation. Currently we have Initiatives mapped to Epics, Features Mapped to Stories and Requirements Mapped to a custom JIRA type of Requireme...
Guest over 9 years ago in Jira 5 Unlikely to implement

Include Area Path in VSTS Integration

I really like the VSTS integration 2.0, however could you add Area Path to the list of available fields that can be mapped to. This would be useful as in VSTS we use Area Path to note which dev team has picked up a feature and it would be great to...
Guest over 6 years ago in Azure DevOps Services and Server 3 Future consideration

Ability to filter records in the ‘integration updates’ based on a field (eg: categories or tags)

Currently Integration update brings in all new records from Rally project. And there is no way to filter the data before import. Want the ability to filter on some Rally fields (eg. status & tags) which will help to import on the required reco...
Jyothirmayi Talaparthy about 4 years ago in Rally 2 Future consideration

Work with Confluence for PRD Documents

Currently we use Confluence PRD documents: https://confluence.atlassian.com/display/DOC/Product+Requirements+Blueprint It would be great if we could find some way to combine this with Aha. Otherwise, we spend time duplicating information from insi...
Guest over 9 years ago in Integrations 11 Already exists

Integrate with Mural

Mural is a great visual management tool. Ideally Mural could be the foundation for the notes section in Aha!. Ideally....you could work on a Mural from within Aha!...so perhaps an integration of some sort. This allows for a virtual room where team...
Guest almost 7 years ago in Integrations 2 Unlikely to implement

Map Created By User from Jira

Currently, when a feature or epic is created in Jira and pulled over to Aha! via the integration webhook, the created by user defaults to the Aha! user who is the webhook "run as" user. Even if there is mapping setup to map the Jira "Reporter" to ...
Guest almost 2 years ago in Jira 1 Already exists

Display Dashboards / Webpages in Tableau

For security reasons, we cannot have Aha! set to "allow anyone to access." Still, we need the ability to provide a seamless experience for our Executives and users to derive value from the Aha! data. We want to be able to display these in Tableau ...
Guest over 1 year ago in Wanted 2 Future consideration

Allow additional Link Types in the 'Links to' field

Within AHA we are mapping Releases -> ADO Release Work Item Master Feature -> ADO Epics Features -> ADO Features. Master Features need to be located in the Release in which they complete. But Features (that contribute to this Master F...
Guest about 5 years ago in Azure DevOps Services and Server 2 Future consideration

Project level automation with Jira

Requesting a change to Aha! Jira integration to allow for project level automation. Project level webhooks send payloads differently than system level payloads. If support for project level webhook payloads were added, we could enable multitudes o...
Guest almost 2 years ago in Jira 0 Future consideration

Ability to copy/move an integration template

We would like to be able to copy and move an integration template from one workspace to another. This would allow us to restrict access on the template if we could move it to a location that no regular users have access to. We can then use that te...
Elaine Edwards over 4 years ago in Integrations 4 Future consideration