-
Add 2-way integration mapping for release start and end dates
Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release.Now that this date is set manually, it should be possi...
0
Future consideration
-
Allow Aha! user name to populate DevOps board user
When working with multiple users, we need to be able who created what, commented on or changed something. As of right now, the user name (Admin) of who configured the Integration (Azure DevOps Services) is the one that appears on every item in D...2 Future consideration
-
Ability to have a choice field (custom) that integrates TWO WAYS with Azure DevOps
Right now we have a choice field of Yes/No/Not Set, but we are unable to integrate it back/forth with Azure DevOps. Not sure why it's being limited with Azure DevOps has the same choice fields. Please open up the integration so we can keep our f...0 Future consideration
-
Configurable destination of imported features
As a product manager, I should have control over the destination of where imported features and epics go so that they are in the release or parking lot where they belong. Today, the destination of imported items seems almost up to chance although...7 Future consideration
-
Allow a single Azure DevOps webhook to support updates across multiple Aha! integrations
With Jira, a single Aha! webhook added at the system level supports updates across all Aha! integrations. This makes scaling integrations simple as after the first setup, a user never has to add another webhook. With Azure DevOps (TFS), ea...0 Future consideration
-
Allow additional Link Types in the 'Links to' field
Within AHA we are mapping Releases -> ADO Release Work Item Master Feature -> ADO Epics Features -> ADO Features. Master Features need to be located in the Release in which they complete. But Features (that contribute to this ...0 Future consideration
-
Improve usability of DevOps iteration field mappings as it relates to import
Azure DevOps does not support webhooks on iterations which means that updates to fields on linked Iterations will not flow from DevOps to Aha! However when specifying the Iteration field mappings in the DevOps integration in Aha!, it is possible t...0 Future consideration
-
Include Area Path in VSTS Integration
I really like the VSTS integration 2.0, however could you add Area Path to the list of available fields that can be mapped to. This would be useful as in VSTS we use Area Path to note which dev team has picked up a feature and it would be great to...2 Future consideration
-
Fix critical Aha to VSTS Integration not syncing Feature Order
We are trying sync the Feature order from Aha to VSTS (never the other way around). Keeping the Features in VSTS in the same order in Aha is in our use case, critical to using the integration. The reason that it fails is because matching the Aha...1 Future consideration
-
Ability to set Aha field to a constant value as part of integration field mappings
My scenario is that I have each Aha product linked to multiple different projects in Team Foundation Server (TFS), and I want the features in Aha that come from TFS to have a field indicating what TFS project they came from. But I can’t find a way...6 Future consideration