PINNED
Chrome extension to capture feedback from anywhere
What is the challenge? We work in many applications and Aha! can not build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? This res...
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
10 months ago
in Integrations
2
Shipped
Allow integrations such as Jira at the Product Line level
Integrations may be common across products within the same product line. It would save time and the possibility to make setup mistakes if these integrations can be setup one level higher
Jira Portfolio adds the Parent Link custom field to Jira. Aha! should support mapping this custom field so that the link between a feature and an initiative in Aha! can be reflected into Jira. This field has the custom field type of "com.atlassian...
The JIRA ID and JIRA Key are reportable attributes within Aha! but they currently cannot be filtered in the reports.
Sometimes where a JIRA ID or Key are known, it would be useful to filter/search Aha! to find this information.
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
12 months ago
in Integrations
1
Shipped
Allow initiatives to sync to integrations as a first class object like features, requirements and releases. For the JIRA integration this would involve: 1. Allow the user to choose the JIRA issue type to sync initiatives with in the integration co...
Rally integration: Add support for custom field integration mappings for two-way custom field updates
We recently made the update where we can populate a required custom field in Rally with a default value to facilitate the integration with required custom fields. This idea is to take it a step further and provide custom field integration mapping ...
When you initially import issues from Jira the Jira comments are not included. This means I have to copy them across manually for every issue - very time consuming. (Comments added to Jira subsequently do appear in Aha.) Please can you include Jir...
Features and Epics should move to integrated parent Release upon updates
What is the challenge? If you introduce Version<>Release mapping to an existing integration or you link a record to an existing Jira record, subsequent updates are creating a new Aha! release (linked to the Jira issues's Fixed Version) but t...