Search results: Integrations
Sort by:
Trending
Filter by:
Status
Showing 27 of 482
1
VOTE
Dependency Relationship Removed does not Update Aha or vice versa
What is the challenge? If a dependency relationship is removed in Azure DevOps, it does not remove it in Aha. If a dependency relationship is removed in Aha, it does not remove it in Azure DevOps. What is the impact? Have to go to both systems to ...
0
Future consideration
13
MERGED
Import from Jira: Ability to use more than one issue type for requirements
Import from Jira: Ability to use more than one issue type for requirements would be useful because we often have Jira Epics mapped to Aha! Features and those Epics have many different types of requirements that we would like to show dependencies i...
2
Shipped
12
VOTE
Set the TFS Iteration and Area path per feature or requirement
Having a single area path for the entire product doesn't make sense. This value will usually depend on the feature, as area paths define the area of code impacted by a work item. This helps with evaluating code churn and test coverage. It needs to...
6
Already exists
9
VOTE
Include JIRA records in linked records
We want to show a dependency of one of our Features on a deliverable from another team without having to create a separate feature and map and sync it through the regular JIRA integration. I think being able to import the JIRA link (and descriptio...
2
Unlikely to implement
6
VOTE
Track dependencies in Pivotal Tracker using Blockers
How this would work:
If an Aha ticket has "depends on" links
Add the Pivotal Tracker ID for each Depended on ticket in AHA that has already been pushed to Pivotal Tracker blocker sections
See PT API document here: https://www.pivotaltracker.com/he...
0
Unlikely to implement
3
VOTE
Add the "[Updating]" tag to Integration Reports where applicable
When you make a change to an Integration being used as a template by other workspace/integrations, while the update is progressing through the dependent workspace/integrations sometimes you see an "[Updating]" tag next to the name in the left navb...
1
Future consideration
6
MERGED
Support different Teams in the TFS integration
We have several development teams on our product, and each has their Team defined under a single TFS Project. It looks like the current TFS integration can only push features to the default team (which is associated with the Project itself). Each ...
3
Already exists
3
MERGED
Mind Mapping tool with Aha
Mind mapping is so important for the product management to visualize the features of the product and help the team to understand it better by pointing relationship, dependencies, risk etc. There are different mind mapping tools available in the ma...
1
Planning to implement
4
VOTE
GitHub integration automatic log time upon linked issue completion
The intended use of GH integration is the following:
Create features in Aha
Push to GitHub as a handover of control to engineering
Updates in GitHub trigger status changed in Aha
This is a good start.
If control is passed to engineering to manag...
2
Already exists
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
© 2025 Aha! Labs Inc.•All rights reserved