My ideas: Integrations
Sort by:
Trending
Filter by:
Status
Showing 962 of 9283
4
VOTE
Integrations 2.0: Allow Master Feature relationship for Requirements
I can create a relationship for Releases at the requirement level even though requirements do not inherently have a release field, this appears to be derived from the feature. I should also be able to create a relationship to the Master Feature in...
0
Future consideration
3
VOTE
Trello cards should contain link back to integrated Aha item
Our product team uses Aha to plan our releases at the Master Feature level. Dev team leaders then "task" these Master Features out as Features and send the Features to Trello, where additional information is added by developers (and where workflow...
2
Unlikely to implement
4
VOTE
Allow fields from linked records to be mapped to integration fields
It would be useful to be able to map additional data from linked records when setting up integrations with my development system.
For example, when configuring the feature field mapping I may want to pass over the initiative a feature is linked to...
0
Will not implement
3
VOTE
Ability to map releases in the same product area to multiple workspaces in Rally
We have times when releases need to be under a particular product in Aha!, yet when they get pushed to Rally, they belong to more than one Rally board. It would be extremely helpful to pick which board in Aha! we are sending the release to in Rall...
0
Already exists
3
VOTE
Ability to push updates to integration that has come from another integration
Long story short.
Our company uses Jira for Customer Service ticketing system and Development team uses Azure DevOps. In between we have Aha! where all features and roadmap is managed. When we take bug fix or improvement task from Customer Service...
0
Future consideration
1
VOTE
Inform user if Version export to Jira fails due to existing fix version in Jira
Problem If a Version is exported from Aha to Jira using the integration, and a fix version with that same name already exists in Jira, Jira will response with HTTP status code 400, and a JSON payload: {"errorMessages":[],"errors":{"name":"A versio...
0
Future consideration
3
VOTE
Ability to aggreate work done value from both feature and requirements
Dear aha, in our scenario when AHA is synced with JIRA with time tracking attributes, we come into a problem with showing the complete work done on the feature when:
1. there is a time log in JIRA on epic (synced to feature)
2. there is a time log...
2
Future consideration
3
VOTE
ability to integrate idea information into Azure DevOps
We use the ideas portal to solicit new enhancements from our users and then link those ideas to features in our products. The problem is only our product management and dev management use Aha. our development team uses Microsoft DevOps to track th...
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
Develop an OSLC REST based connector for Aha!
We need to link Aha! Roadmap items to other items in Sparx EA (OSLC compliant) using ArchiMate 3.1 and an OSLC connector for Aha! will enable us to do that. This connector will also enable us to link Sparx EA ArchiMate 3.1 model elements such as s...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved