Allow switching between integration templates if they are integrated with the same project
What is the challenge? As part of a migration, we are planning to change existing integrations and switch from using "Template A" to "Template B". The challenge is that "Template B" is not available for selection unless it is integrated with the s...
Dale Potter
7 months ago
in Integrations
2
Shipped
Aha! + JIRA feature/story relationships (e.g. is blocked by, depends on) should match
If one feature depends on another, and you create that dependency in Aha!, it will not be reflected in JIRA currently. If Aha! and JIRA feature/story relationships were maintained back and forth, then we could create more realistic roadmaps and st...
As a developer, when I change a story's epic / fix version (i.e. Aha! feature / release) I want that change reflected in Aha! so that my Product Manager will know that a story or bug was pushed out to the next release
Rather than have to manually push ideas to the integration with Azure, Jira or other systems, it would be helpful and reduce manual administration if the automation rules could include the capability to send on a condition such as a status change....
Ronnie Merkel
about 4 years ago
in Integrations
3
Shipped
Our organization is moving from Slack and into using Microsoft Teams. We would like to have our Aha! activity feed integration be compatible with Teams.
Jon Kremer
over 8 years ago
in Integrations
20
Shipped
Update Microsoft Teams integration to not use connectors
Microsoft is deprecating Office 365 Connectors: https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/ Please update the Microsoft Teams integration to support workflows or a new app entirely. De...
Nathaniel Collum
9 months ago
in Integrations
1
Shipped
Product implementation and execution schedule can be build up with much more detail in smartsheet. A combination of aha! and smartsheet can be a much more powerful tool for our customer.
Ability to link features/requirements to existing VSO work items
Current VSO/TFS integration only allow to submit a feature/requirement from Aha! to TFS/VSOAn option to link a feature/requirement with an existing TFS/VSO work item would be helpful
Aha now honors additional Jira Types (other than just Stories and Features) - YAY! However, when the Jira Type is changed, it breaks the sync between the Jira item and Aha item.
Example: Support reports a "Support Defect", Dev reviews, changes it...