Integrations

In my organization we have separate Aha! accounts for each business unit. We use one Salesforce instance across our organization. I would like to be able to integrate our multiple Aha! accounts with our Salesforce instance.

When mapping an initiative to a record in a development tool, it would be helpful to have the ability to map the "assigned to" field from Aha! to a user field. This would be helpful when initiatives are mapped to EPICs so the assigned user can syn...

Some comments are for testing purposes or are not correct. If we have decided to delete a comment from an epic or story in Jira, we would like it to be removed from the feature in Aha! as well.

As a company adopting a next generation performance management system anchored in the concept of Objectives and Key Results I would like to synchronize Aha goals, success metrics and initiatives with BetterWorks (www.betterworks.com) Note: both Be...

In Aha!, if you have enabled 'Delivery risks', one of the things you can do is manually set a flag on a Feature (or Epic or Requirement). In Jira, you can also 'Flag' issues similarly. Aha!: https://www.aha.io/support/roadmaps/strategic-roadmaps/c...

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...

Right now - when tagging someone in Aha! it links the user on Aha! to the comment e.g. Comment by XXX@YYY (link to user in Aha!) .... But it is useless to have it that way - it would be much nicer if the tagging on the comment in Aha! corresponded...

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

Currently only fields that are mapped one-way from Aha! to Jira will update when imported to Aha! - we import records from Jira to Aha! without a version set in Jira and Aha! automatically adds them to a default release in Aha! - we would like Aha...

Who would benefit? Everyone What impact would it make? Allows for further data collection from SFDC in Aha! How should it work? Similar to how other SFDC fields are currently mapped in today's configuration.