Integrations
Sort by:
Trending
Status:
Unlikely to implement
Showing 943
2
VOTE
1
VOTE
Allow link of a requirement to a release (sprint)
We have features that are mapped to a specific sprint, but within that feature, we have requirements (user stories) that could be mapped to two different sprints. The assumption with Aha! is that a feature would be completed in one sprint, which i...
0
Future consideration
4
VOTE
Only update Jira FixVersion if the Release has actually changed in Aha and the Jira FixVersion has not been edited
In my process I want Aha to be my master in terms of planning, but allow Jira to update details as actual releases are made. By this I mean that I will plan a release such as "Q4 2017" in Aha and push to Jira. As work is completed in Jira the issu...
0
Unlikely to implement
2
VOTE
Provide the ability to map the Release field from a Feature or Epic to an external system such as ADO
Given that AHA is all about releases and ADO is all about time lines, the concept of a Release in AHA is quite different than what exist in ADO - yet there is a Target Release field in ADO as well as in the Feature of AHA - please can this be expo...
1
Future consideration
2
VOTE
Advanced Integration with Zapier
I was trying to do an integration between Freshdesk and Aha, and since there is no direct integration, I used Zapier, however, the fields available at Zapier are just the idea title and description, all the custom fields I have on Aha's ideas are ...
0
Future consideration
2
VOTE
Sync Sprints betweeen Aha! and Rally
As product owners use Aha as the primary repository to develop and track their roadmap, they want to enhance their planning phase by improving the existing configuration between Aha and Rally. Currently, capabilities, features, and user stories ar...
0
Future consideration
3
VOTE
improved metadata rest services for fields
For users trying to interface with the Aha service via the rest services there is a definite lack of available services for fields.
There needs to be a way to validate fields being sent to Aha. Currently there are only services that return filed d...
1
Future consideration
4
VOTE
Assignee of feature in Aha! should propagate to Gitlab
As a user of Aha! / Gitlab integration, I would like to assign a feature in Aha to a specific user and have it show up as assigned to them in Gitlab, so that they are aware of the new feature and can take responsibility to break it down further in...
0
Future consideration
4
VOTE
5
VOTE
Salesforce integration without permission set
Currently, the Salesforce / Aha.io integration requires using a permission set. A System Administrator must assign individual users in Salesforce to this permission set, in order for them to use the Aha.io ideas portal. That's a fine approach, but...
1
Unlikely to implement
© 2024 Aha! Labs Inc.•All rights reserved