Integrations

What is the challenge? I work in a G suite company where all my work funnels those tools. What is the impact? I do not check or follow-up on Aha! to-dos because I don't have regular visibility. Describe your idea Allow a two-way integration betwee...

Please enable the ability to sync a release phase to an Epic in Jira. And also sync release phase To-Dos to tasks in Jira. Use Case: I have a release template with my release phase and associated to-dos. These to-dos are what govern my Jira tasks....

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

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

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.

What is the challenge? If a dependency relationship is removed in Azure DevOps, it does not remove it in Aha. If a dependency relationship is removed in Aha, it does not remove it in Azure DevOps. What is the impact? Have to go to both systems to ...

Issue? The default Rally integration record mappings are Feature / Release / Requirement. Every new integration is being given the three record default which is confusing Aha users and enables users to deviate from the best practice of feature to ...

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.

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

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