ADD A NEW IDEA

FILTER BY CATEGORY

Azure DevOps Services and Server

Showing 95

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...
Guest about 2 years ago in Azure DevOps Services and Server 0 Shipped

Azure DevOps or JIRA integration : allow some way to automatically select which integration to use when more than one exists in a product

We usually map 1 Aha Product to 1 AzDo project, in which case everything is fine (except that everything ends up in the same Area Path).We can also easily map N Aha Products to 1 AzDo project, mapping each Product to an AzDo area path. But we curr...
Guillaume Metman about 2 years ago in Azure DevOps Services and Server 0 Future consideration

Add more detailed error logging for Azure/TFS

No description provided
Guest about 2 years ago in Azure DevOps Services and Server 0 Shipped

Automatically create webhooks by default for Azure/TFS

No description provided
Guest about 2 years ago in Azure DevOps Services and Server 0 Future consideration

Keep features in sync when they cross areas in Azure DevOps

This is useful when you have your DevOps areas configured by team. Once the features are pushed from Aha! to DevOps and evaluated by the team they need to be moved into the area for the appropriate team. Any team can work on any feature based on a...
Deb Gay about 2 years ago in Azure DevOps Services and Server 0 Future consideration

Configurable unit of time for Estimation field

We're using Aha with Azure DevOps integration. We’ve mapped the Estimate field in Aha with an estimate field in Azure DevOps. Our estimation process is basically as follows: * Product Manager creates Feature in Aha * Product Manager send RFC in...
Guest over 2 years ago in Azure DevOps Services and Server 7 Future consideration

Map VSTS/TFS picklist custom fields to Aha! choice list fields

VSTS/TFS picklist custom fields are treated as strings and cannot support option mappings. Mapping a picklist field to an Aha! choice list field should provide the option to click Configure and map the choices.
Tessa Adair over 2 years ago in Azure DevOps Services and Server 8 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...
Tessa Adair over 2 years ago in Azure DevOps Services and Server 7 Future consideration

Converting requirements to features after integration

Converting a requirement to a feature will cause the record to lose some custom field information because features may not have the same custom fields. We can choose whether or not to proceed. There's no mention of integration to an external sys...
Tom Beck over 2 years ago in Azure DevOps Services and Server 1 Future consideration

Properly transfer images in VSTS comments to Aha!

Currently, if a user adds a comment to a User Story or Bug discussion in VSTS and embeds an image in the comment, the image doesn't come through with the comment that shows up in Aha!. This makes it difficult for the reader in Aha! to follow the d...
Guest over 2 years ago in Azure DevOps Services and Server 0 Future consideration