Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 953

Support multiple scrum boards

Some Jira projects leverage multiple scrum boards within a single project; it would helpful if the Aha! integration could accommodate that.
David Strathy-Miller about 3 years ago in Jira 0 Future consideration

Set the TFS Iteration and Area path per feature or requirement

Having a single area path for the entire product doesn't make sense. This value will usually depend on the feature, as area paths define the area of code impacted by a work item. This helps with evaluating code churn and test coverage. It needs to...
Jonathon Leeke over 9 years ago in Integrations 6 Already exists

Persistent filters for integrations and incoming product updates

Using JIRA integrations, I have an Aha product that spans several JIRA projects. To work with this I have set up an integration per project with a specified JQL filter. For example my filter could include "priority = high". Other products througho...
Guest over 6 years ago in Jira 0 Future consideration

Set Default Filters for Integration Updates

Provide the ability to set default filters on the integration updates Feature. I have Product Owner access in multiple products to assist with managing the layouts and set up of the products in Aha, but I do not want to worry about accidentally ...
Guest about 7 years ago in Integrations 0 Future consideration

Integrate Ideas with UserVoice feedback

Our support team has adopted uservoice as our support platform. They're using this to collect feedback on the product. It'd be great if we could integrate this into Aha's own ideas list
Guest over 10 years ago in Wanted 2 Unlikely to implement

Pivotal Tracker Integration Mapping

It would be helpful if one of the mapping options with Pivotal Tracker could include the following options: Master Feature to Epic Feature to Story Requirement to Task Instead, the only option for mapping to Epics in PT is to use Initiatives. Th...
Tom Beck over 6 years ago in Pivotal Tracker 1 Will not implement

More complete field mapping between Aha! and FogBugz

Both products are feature rich and have many alignments which would be great to keep in sync. Aha! Feature Type - FogBugz Case Category FogBugz has an "Area" concept which doesn't map directly. At least being able to select the target area for ne...
Guest over 9 years ago in Integrations 4 Will not implement

Sync story points to Jira without Capacity Planning

My teams doesn't use capacity planning, as we have the same team members each week, but we'd like to be able to automatically link story points to Jira. Currently this is only accomplishable when you have enabled capacity planning, which causes me...
Michael Clinton almost 9 years ago in Jira 1 Future consideration

Copy integration mappings for records at the same hierarchy level

When configuring an integration between Aha! and a development tool, you decide what records in Aha! map to what records in the development tool and map the individual fields. It's common to have multiple record types in a development system at th...
Emily Yankush over 1 year ago in Jira 0 Future consideration

Allow mapping fields from related records in Aha to Azure Devops

This idea is to allow mapping fields from related records from Aha to DevOps. In most cases, this would be parent/grandparent/great grandparent situations. For example, allowing a tag from an Aha feature to be mapped to a tag on a DevOps PBI. Anot...
Josh Wayne about 3 years ago in Azure DevOps Services and Server 0 Future consideration