Skip to Main Content
ADD A NEW IDEA

My votes: Azure DevOps Services and Server

Showing 96 of 8548

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 ...
Tom Beck about 6 years ago in Azure DevOps Services and Server 9 Future consideration

DevOps Integration -- Support rendering of images embedded in description field

Currently when you import from Azure DevOps, if you have images embedded into the description field, they come over as a link in the Aha! description field, e.g. imagename.png. It would be great if they would render in Aha! like they do in DevOps....
Mike Maylone over 3 years ago in Azure DevOps Services and Server 9 Future consideration

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 poss...
Austin Merritt about 4 years ago in Azure DevOps Services and Server  / Integrations / Jira / Rally 1 Future consideration

Allow attachments to Feature comments to be integrated to Azure DevOps

When you add comments to a Feature, and you have integration with Azure DevOps (ADO) configured, you can have these comments passed back and forth. Unfortunately if you attach a file to a comment it will not get passed between Aha and ADO. When yo...
Guest over 3 years ago in Azure DevOps Services and Server 0 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 about 5 years ago in Azure DevOps Services and Server 9 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...
Guest over 4 years ago in Azure DevOps Services and Server 1 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 almost 5 years ago in Azure DevOps Services and Server 0 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...
Guest over 5 years ago in Azure DevOps Services and Server 2 Future consideration

VSTS Requirement ToDo's

Can we get the VSTS Requirement To Do's transferring over as user story tasks?
Guest over 7 years ago in Azure DevOps Services and Server 3 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...
Guest over 5 years ago in Azure DevOps Services and Server 3 Future consideration