Integrations
Sort by:
Recent
Filter by:
Status
Showing 916 of 8640
8
VOTE
Do not allow requirements to be mapped without a Links To relationship set
It is possible to create an integration where you have requirements mapped to a Jira record type, and where you have no Links To relationship established to a parent record in Aha! This results in import errors where requirements cannot be importe...
0
Future consideration
12
VOTE
Provide alternative way to match users when email address is not exposed in Jira
Some time ago, Atlassian made changes that requires users to share their email addresses on an individual user profile setting. When that option is not checked, Aha! is not able to view their email address and if assigned user is mapped, is not ab...
1
Future consideration
17
VOTE
Warn when there are incomplete Jira webhook settings
When setting up a webhook in Jira, you can choose specific events to trigger the webhook event. Some users accidentally select "Exclude body" which results in empty webhooks returning to Aha! and no updates being made. Other users create the webho...
0
Future consideration
3
VOTE
Provide integration between AHA and HCL Compass / IBM ClearQuest
A integration between AHA and HCL Compass / IBM ClearQuest would allow Features/Epics to be shared with the workflow tools Compass and ClearQuest As Product Manager for ClearQuest and Compass we would welcome this integration for our joint custome...
0
Future consideration
16
VOTE
Change revision history descriptors for text field updates
It seems that some fields when updated via integration show a descriptor as XYZ changed integration link for Capability..123". This can be found in some values fields. Other fields like description simply state " XYZ updated the capability 123". T...
1
Future consideration
5
VOTE
New features created via an ADO integration are assigned to the parent epic release by default
Key problem: the "Parent" field in ADO can contain only one value. In ADO, a feature is automatically associated to the same theme as its' parent epic, but in Aha! this is not the case. So when features import, we associate them with the correct p...
0
Future consideration
1
VOTE
8
VOTE
Integrating with a specific Jira board
It would be helpful if we could use the Jira integration to send features to a specific board. We have several dev teams working within a single project, but they utilize different broads. We would like to send a feature to open a record is a spec...
1
Future consideration
2
VOTE
Add Boolean Field mapping for Rally 2.0 Integration
Currently, there is no way to map Boolean fields in Rally to Predefined Choice fields in Aha. A Boolean field in Rally can only be mapped to a text field or a few other options like Aha Rank, and can only bring the data from Rally to Aha, not the ...
0
Future consideration
2
VOTE
Calculated mapping of number fields in integration with Jira
We would like to specify a conversion factor or formula to map numeric fields between Jira and Aha! numeric fields, especially a Jira number field and Aha!'s Original Estimate field. This would allow us to enter hours into a Jira number field whic...
0
Future consideration