Integrations
Sort by:
Popular
Status:
Unlikely to implement
Showing 136
2
VOTE
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,...
1
Unlikely to implement
2
VOTE
Merge Custom Fields into One Field when they are carried over from Idea to Feature
At idea stage you capture information about the idea in multiple fields, when you promote this to a feature if this information was merged into one 'Body' field, then I would save time not having to copy and paste those fields into one field.
Ha...
0
Unlikely to implement
2
VOTE
Integration Updates > Send Changes > Add Release filter & Status filter
On the Aha! Integration Updates screen for an Aha! to/from Jira Integration, I would like to see which releases and the status of what each of the items are for integration. Being offered these filters would allow me to select that before importin...
1
Unlikely to implement
2
VOTE
Mockups, Axure Integration
For wireframes / mockups we are currently using Axure.
It would be great to be able to use that instead of the Aha! build-in tool. When I think about it, your tool is rather a diagramming tool like LucidChart. To call it "mockup" is misleading in ...
1
Unlikely to implement
2
VOTE
Manual selection of items selected for import from Jira
As a user of Aha! and Jira I want to be able to select the items that get imported from Jira so that I can more easily coordinate and synchronise the data held in the two products.
There are two main tools that allow data to be brought into Aha! f...
0
Unlikely to implement
2
VOTE
2
VOTE
Support iovation LaunchKey for Multi-Factor Authentication
Currently you seem to only support stronger authentication options for those customers who use Duo (under their own contract). While we would be OK with an Aha! contracted strong authenticator, if we must supply our own then our preference would b...
0
Unlikely to implement
2
VOTE
JIRA and Aha synchronized numbering
We understand that the IDs in AHA and JIRA are meant to be treated as separate IDs without a true association between the two systems. However our workflow allows us to use the same IDs in both systems, assuming we enter them in the same order. Ho...
0
Unlikely to implement
2
VOTE
2
VOTE
Would it be possible to not need a paid AHA account to process VSTS updates?
At the moment we have set up the VSTS integration with a paid AHA account as required. This means that all updates come in from that product manager. In the history threads, and the notification emails we get a combination of VSTS updates, and the...
1
Unlikely to implement