The ability to retrieve options for single/multi selects using REST
When updating an item via the REST API it would be good to know what the possible values are for single/multi selects. This would also allow mapping the options to options in another system in an Aha! integration.
See who in my support team voted on or created an idea in our ideas portal from Zendesk integration
We are using our sales and support teams to enter customer requests in to our ideas portal. Inevitably this is an extra chore that doesn't short term help them get their job done quicker, but should do in the long run! So as product manager I need...
almost 5 years ago
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...
VSTS Integration - Error importing new records into Aha
As we are starting to use more and more Aha!, we are seeing errors while newly created records by Development team in VSTS being imported into Aha!. 2 main reasons for the errors include
Feature is not available for the user stories (Requiremen...
Allow parking lot features and releases to not be sent to Jira
I use the parking lot to prepare for my upcoming releases thus the release name is not in Jira. These are also stories that do not need to be in Jira yet. With integration turned on I get an error every time I move a feature around in the parking ...
about 5 years ago
I would like to know how the Original Estimate and Work Done fields are configured in Aha!. I have mapped (Jira)Total Story Points to (Aha!) Original Estimate and (Jira) Completed Story Points to (Aha!) Work Done. I'd like to know how to these pop...
Our product team has just started using aha to keep track of product development. Mean time in the individual teams we are free to choose what ever tool we like and fits our needs, and for that I've chosen coda.io. Coda.io have a feature where you...
when syncing master features and linked features to VSTS, have relationship between these items persist on the VSTS Side
Here is issue:
Create Epic in AHA
Create Feature in AHA, linked to Epic above
Sent Epic from AHA to VSTS
Sending Epic to VSTS does also automatically send the Feature from AHA to VSTS. However, the Epic and Feature in VSTS are not linked.