Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 953 of 9212

Rest services for metadata validation

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 almost 6 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 almost 6 years ago in Jira 0 Future consideration

Add 'Status' Column to the Aha Idea Links Related List on Object Records

I want to be able to show the status of the idea from the Account page layout on the related list, but the Status field is not an available column.
Eliza Crawford almost 6 years ago in Salesforce 2 Future consideration

Custom Record Type, Made Up Entirely Of Custom Fields

We have some customer systems that we need to sync data back from. These are generally tasks that are created in systems we integrate with (specifically Azure Dev Ops, with the Task record). We are an outsourced product management company, so we h...
Guest about 4 years ago in Azure DevOps Services and Server 0 Future consideration

Rally Integration - Rewording Excluded Child Updates

As a Rally Admin, this wording can be be quite confusing. I've had to explain it several times to users. Suggestion: Instead of Excluding, "Included Child Updates" - box is automatically checked, so users can uncheck if excluding those updates.
Victoria Morrella about 4 years ago in Rally 0 Future consideration

Allow link of a requirement to a release (sprint)

We have features that are mapped to a specific sprint, but within that feature, we have requirements (user stories) that could be mapped to two different sprints. The assumption with Aha! is that a feature would be completed in one sprint, which i...
Guest about 2 years ago in Azure DevOps Services and Server 0 Future consideration

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 about 8 years ago in Integrations 1 Will not implement

GitHub integration automatic log time upon linked issue completion

The intended use of GH integration is the following: Create features in Aha Push to GitHub as a handover of control to engineering Updates in GitHub trigger status changed in Aha This is a good start. If control is passed to engineering to manag...
Guest about 8 years ago in GitHub 2 Already exists

Provide options to prevent Sending over to Jira via integration if Status is not equal to a specific status

We need a way to prevent an end user from selecting the option in Integrations to Send to Jira unless the Status = Open. With it set to any other status, it causes Integration issues. We dont want to have to set up approvals to verify this. Just w...
Guest about 4 years ago in Jira 1 Future consideration

Tickets linked to JIRA should link back to Aha.

We are currently pushing Aha! tickets into JIRA. It would be helpful to have a link in Aha-created JIRA tickets that linked back to Aha (the same way Aha! has a ticket number and link to the JIRA ticket).
Guest about 8 years ago in Jira 0 Already exists