Currently we cannot push work back from Azure to Aha correctly as the releases/Iterations do not sync which causes manual work to move a card to the correct Aha release once imported. Iterations can be nested in ADO, and when you try to send recor...
Update records on all integrations linked to a template at one time
We anticipate having 150+ integrations based on a template (with the Rally integration). In order to add fields to the integrations, we edit the template and those updates/new fields flow to the individual integrations based on the template, howev...
Elaine Edwards
about 5 years ago
in Rally
2
Future consideration
You have implemented OneDrive for Business - however it only allows attaching files from my own document library. I'd like to be able to attach files from other Sharepoint online document libraries - such as those created through 365 Groups and Te...
David Behr
almost 7 years ago
in Wanted
4
Future consideration
Need full two way integration of a Story with VSTS
Right now you can push a Feature and associated stories to VSTS but if you delete a story in VSTS you have to manually delete in Aha. We need:
1) any story delete in VSTS to be automatically deleted in Aha
2) any story added in VSTS to a Feature...
We move customers from opportunity into lead generally before we can capture their ideas. They are then leads for their lifetime with our business. With the current Aha! Salesforce integration, we can't capture their ideas through Salesforce.
Melih Onvural
almost 9 years ago
in Salesforce
3
Future consideration
Deleting a feature or requirement should delete the linked Jira issue(s)
When I delete a feature or a requirement in Aha!, I then have to go to Jira and delete the corresponding epic or story. Would love it if deleting a feature in Aha! deleted the linked epic in Jira and all stories for that epic. Likewise, deleting a...
Guest
over 10 years ago
in Jira
11
Will not implement
In both Jira and Aha!, you need to have a user that has the appropriate permissions which is often a highly privileged user. However, when setting up the integration, there is no way to indicate an alias name to use for the integration. Consequent...
Karie Kelly
almost 3 years ago
in Integrations
0
Future consideration
This request is to support the mapping of ADO boolean fields to Aha predefined droplist and tag fields. Currently, Azure DevOps Boolean fields (true/false) cannot be mapped to Aha fields. Rather, in ADO, you need to create a field as a picklist in...
We have the following workspace hierarchy; Product Line A Product B Product C Each Product is setup to integrate with a different Jira Project. If I create a feature in Product C and link it to an initiative in Product Line A, the following happen...
Bill Simakis
almost 5 years ago
in Jira
1
Future consideration
JIRA integration needed at the portfolio and product family levels.
We use initiatives at all levels within Aha and need to be able to integrate those with JIRA for additional capacity reporting. If initiatives are available to be entered on those levels, it would be useful to have the integration setup available ...
Wen-Wen Lin
over 5 years ago
in Jira
2
Future consideration