The pivotal integration only allows for 2-way integration only if originally pushed from aha initially. Even then it's pretty limited to status and description.
If I create an 'feature' in aha which maps to an 'epic' in pivotal, and someone add...
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 c...
about 7 years ago
I’m not sure if Invision supports an API yet, but it would be an ideal integration for Aha. Right now, I think Aha does a great job of what I would call the front end of the funnel for product management: capturing ideas, managing a backlog, high ...
about 8 years ago
Ideas coming from an Aha customer portal to be linked to the account in SFDC automatically
When a customer submit an Idea in our Customer facing portal the Idea should be linked automatically into that users account on SalesForce,
Today we are able to go into SFDC and manually search for the Idea for that user and link the account to t...
about 3 years ago
Allow users to push information from Aha! into ClickUp and vice versa. A product roadmap/plan from Aha! could ideally be plugged directly into tasks in ClickUp.
A project manager would then create their roadmaps in Aha! while the team works in th...
over 5 years ago
Unlikely to implement
Move Aha! Requirements when linked JIRA Stories are Moved to a different Epic/Feature
The specific use case that this commonly occurs for is the following mapping:
Feature = Epic and Requirement = Story; however, the same would apply to other mappings parent child mappings such as Story/Sub-task as well.
Current behavior: The i...
over 6 years ago