Though we have Iteration path integration between Aha and ADO. This is currently limited to show dynamic values for the integrations. Also the Iteration Path is based on the Area Path, the values of Iteration path cannot be filtered / shown releva...
Many products are using Metis exclusively, especially those who are waterfall and do not need a JIRA instance. If Metis is not integrated with Aha! similar to JIRA, these product owners will be left managing timelines and updates from Metis on the...
Guest
almost 2 years ago
in Integrations
0
Future consideration
For developing systems that integrate with Aha.
It would be really useful to query the Rest services for a particular Aha object to determine what fields are required to create or update that object. That way validation can be performed programmat...
Tim McCaskill
over 5 years ago
in Integrations
1
Future consideration
Improved error message on incorrect JIRA record type link
Using the JIRA 2.0 integration, if you try to link to an existing record type that is not mapped in the integration config, the error message is very unhelpful. It just says "system error - contact Aha support if this persists" (or something like ...
Mat Wood
over 5 years ago
in Jira
0
Future consideration
Alternative JSON format for changes property in Activity webhook
We are attempting to read changes to the Ideas record type using the Activity webhook.
Most of the information is straight forward, in an expected JSON format.
But for changes, the data comes through as an array of json objects, instead of p...
Erin Quick-Laughlin
almost 2 years ago
in Integrations
1
Future consideration
We're working on an integration where we'd like to know the plan name for the product. For example we'd like to distinguish whether the plan is Ideas Advanced or Ideas Essentials. On the similar lines we'd also like to know for Roadmaps the plan n...
Guest
almost 4 years ago
in Wanted
1
Future consideration
We have many users that have asked me for the ability to search for a Feature based on it's Jira Key. Currently the only way to do that using the Search box is for them to add the Jira Key to the Feature description, and they don't want to have to...
API - support sending multiple parameters/values in search query
The API currently only accepts a single value search parameter. There is a requirement to be able to pass multiple parameters/values through the API. For example, execute a search through the API for features that contain 3 specific tag values.
Matt Case
over 7 years ago
in Integrations
1
Will not implement