Sometimes it is difficult to keep Jira and Aha Requirements up to date when/if a requirement is deleted. I'd like to see a Mapping that is allow to delete and you can select which direction that can occur.
Kenny Burnham
almost 6 years ago
in Jira
2
Unlikely to implement
If one of my business partners used Aha! -- I'm trying to sell them on it -- it would be really cool, in theory, to be able to integrate with their instance. They currently use Pivotal Tracker and I integrate some features with them. If they moved...
Tom Beck
almost 6 years ago
in Wanted
0
Unlikely to implement
Micro Focus ALM Octane is a comprehensive lifecycle management solution that accelerates enterprise Agile transformations for high- quality application delivery at enterprise scale while leveraging existing investments. The flexible platform integ...
Guest
almost 6 years ago
in Integrations
0
Unlikely to implement
Hi,
Trello Integration is already cool, we can flexibly map various Trello fields to various Aha fields, and for some fields also specify how particular Trello values map to particular Aha values.
However, this still assumes that for every Aha fie...
Guest
almost 6 years ago
in Trello
0
Unlikely to implement
Add a one way data integration from CA Agile Feature Actual Start/End Date into AHA features as view only
When integrating with CA Agile, we can pass feature planned dates between both applications. When the execution/delivery teams begin work on a feature, the feature actual start date is systematically updated. This date is sometimes different from ...
Guest
almost 6 years ago
in Integrations
0
Unlikely to implement
A way to execute saved queries, or use a query language (such as the filter options in the web UI) with REST
This would allow users of the integration to narrow down the scope of items being retrieved to improve performance and create less unnecessary traffic on the Aha! repository.
Guest
almost 6 years ago
in Integrations
0
Unlikely to implement
A way to retrieve all the fields, including custom fields, and metadata for an item type (eg. Feature) using REST.
Field information would ideally include the type of the field (string, number, drop down, etc.), and properties such as if it is a required field or read only field. This would allow the integration to know what fields are available when creating,...
Guest
almost 6 years ago
in Integrations
1
Unlikely to implement