Integrations
Sort by:
Popular
Status:
Future consideration
Showing 642
2
VOTE
2
VOTE
Update Asana integration to use milestones
Asana introduced Milestones in 2020. These are closely analogous to Aha releases. The only option to link a release in Aha is to a column in Asana - I guess because there was no Milestone at the time. This is now not ideal and means that we cannot...
0
Future consideration
2
VOTE
Configure iterations based on phases in DevOps
We're using multiple layers of iterations within Azure DevOps. So a Release consists of multiple sprints. I would like to be able to map not only releases to iterations, but also phases to iterations. That way I can use Aha! as a single point of e...
0
Future consideration
2
VOTE
Custom Record Type, Made Up Entirely Of Custom Fields
We have some customer systems that we need to sync data back from. These are generally tasks that are created in systems we integrate with (specifically Azure Dev Ops, with the Task record). We are an outsourced product management company, so we h...
0
Future consideration
2
VOTE
Rally Integration - Rewording Excluded Child Updates
As a Rally Admin, this wording can be be quite confusing. I've had to explain it several times to users. Suggestion: Instead of Excluding, "Included Child Updates" - box is automatically checked, so users can uncheck if excluding those updates.
0
Future consideration
2
VOTE
Provide options to prevent Sending over to Jira via integration if Status is not equal to a specific status
We need a way to prevent an end user from selecting the option in Integrations to Send to Jira unless the Status = Open. With it set to any other status, it causes Integration issues. We dont want to have to set up approvals to verify this. Just w...
1
Future consideration
2
VOTE
API to get plan details for an account
We're working on an integration where we'd like to know the plan name for the product. For example we'd like to distinguish whether the plan is Ideas Advanced or Ideas Essentials. On the similar lines we'd also like to know for Roadmaps the plan n...
1
Future consideration
2
VOTE
Support bi-directional flow of data when mapping Aha! releases to Jira sprints as a field mapping for features
Use case: Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.
0
Future consideration
2
VOTE
Parent version mapped to 2 different releases - let user decide where to import
The same Jira version may be associated with releases from more than one Aha! workspace. This can happen when different products in Aha! are all being released together. When auto-import is enabled on the integrations and a new record is created i...
0
Future consideration
2
VOTE
Allow Integration variable on Create Record layout
Currently when creating a feature, I have to create the feature and then manually send the integration to ADO. I want to have a variable on the Create Record Layout screen to be able to choose this option when creating the feature. This way I can ...
0
Future consideration