Currently, when you change the type of record for an integrated record in ADO, it somewhat breaks the integration. Updates are still sent from Aha! to ADO but updates are not processed from ADO to Aha! It appears this scenario is supported for Jir...
Guest
11 months ago
in Integrations
0
Future consideration
It would be helpful if one of the mapping options with Pivotal Tracker could include the following options:
Master Feature to Epic
Feature to Story
Requirement to Task
Instead, the only option for mapping to Epics in PT is to use Initiatives. Th...
Tom Beck
about 7 years ago
in Pivotal Tracker
1
Will not implement
Change default visibility of ideas submitted via Slack
I recently installed the Slack integration. When one of our team members submits an idea via Slack, it shows up in our Aha dashboard but not on the associated portal page. As of right now, I believe I'd have to change the visibility of each new id...
Guest
about 7 years ago
in Ideas / Slack
0
Future consideration
Show comments added in JIRA as part of a state transition.
Currently, when a comment is add to a JIRA issue as part of a state transition, the comment is not shown in AHA.
This is a real issue for us since the Engineering team adds useful comments in JIRA when they move an issue between states. This means...
Michael Buonassisi
over 6 years ago
in Jira
2
Future consideration
Removing account link from an idea in Aha! should remove the link on the account in Salesforce
Using the Salesforce integration, if you remove the request on the Idea page (by clicking on the bin icon) and go to the related account in Salesforce, the request is still listed there. Ideally this would update Salesforce dynamically.
Gergo Navratyil
about 9 years ago
in Salesforce
0
Future consideration
The Product Name contains an import department work categorization that we would already use to filter reports in Aha and would like to be able to do the same in JIRA. There is a similar request to have Product Name in the Slack integration. I won...
Wen-Wen Lin
over 6 years ago
in Jira
0
Future consideration
Allow VSO integrations to work with multiple Aha Products represented in a single VSO Project
Some customers have specified that they maintain a single VSO Project, but represent a number of products beneath it. The way to handle that now in Aha is to set up a web-hook for each product in Aha, and then create a subscription in VSO that fil...
Support Movement of Requirements to Different Features in Other Workspaces
We recently integrated JIRA stories mapped to Aha! requirements but are running into an issue with stories moving from JIRA epic to JIRA epic. Currently, Aha! supports stories moving from epic to epic, but only if those epics are mapped to feature...
Anh Truong
over 4 years ago
in Jira
1
Future consideration
What is the challenge? We leverage Adobe Analytics for a lot of analytics and reporting. It would be great to have a direct non-third-party integration. What is the impact? Allowing for synergy between our goals and roadmaps in Aha! and our report...
Guest
11 months ago
in Integrations
0
Future consideration