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...
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
about 1 year ago
in Integrations
1
Shipped
Add an "Import from Rally" utility for uploading the Rally backlog into Aha!
Add an "Import from Rally" utility for importing existing features, user stories, etc. and supporting metadata into Aha! as Features and Requirements and creating corresponding links between the data objects in support of the bi-directional integr...
Currently the Aha! to Salesforce integration must be installed using the classic interface. After that, it can be used via the Lightning interface. As a Salesforce admin, it would be nice to be able to install the app via the Lightning interface a...
Scott Goldblatt
over 8 years ago
in Salesforce
15
Shipped
Add 2-way integration mapping for release start and end dates
Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release. Now that this date is set manually, it should be poss...
Link existing GitHub issues with a new Aha! Feature
The current Aha! - GitHub integration lets you sync features to GitHub issues. This won't work in the opposite way. However, It'd be nice to have an editable field to reflect that the Aha! feature is linked to a GitHub issue.
We would like the ability to have new records created in JIRA/Rally automatically import into Aha!
Currently, they have to be accepted in Aha! prior to import. This causes an extra step in our workflow we do not wish to have to go through each time.
Danny Archer
over 7 years ago
in Integrations
7
Shipped
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...
Map Jira's "Won't Fix" resolution status to Aha!s "Won't implement" status
When the Jira workflow is set up to "Close" a ticket with the resolution status of "won't fix," there currently is now way to map that against the Aha workflow.
It would be great to also access the Resolution status from Jira to handle this case.