ADD A NEW IDEA

FILTER BY CATEGORY

Azure DevOps Services and Server

Showing 53 of 6649

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 over 2 years ago in Azure DevOps Services and Server 8 Future consideration

VSTS Requirement ToDo's

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

Need full two way integration of a Story with VSTS

Right now you can push a Feature and associated stories to VSTS but if you delete a story in VSTS you have to manually delete in Aha. We need: 1) any story delete in VSTS to be automatically deleted in Aha 2) any story added in VSTS to a Featur...
Eric Reichel about 4 years ago in Azure DevOps Services and Server 1 Unlikely to implement

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 2 years ago in Azure DevOps Services and Server 3 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...
David Greenwood almost 2 years ago in Azure DevOps Services and Server 1 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 1 year ago in Azure DevOps Services and Server 3 Future consideration

Allow VSO integrations to work with multiple Aha Products represented in a single VSO Project

Some customers have specified that they maintain a single VSO Project, but represent a number of products beneath it. The way to handle that now in Aha is to set up a web-hook for each product in Aha, and then create a subscription in VSO that fil...
Alex Bartlow almost 5 years ago in Azure DevOps Services and Server 1 Unlikely to implement

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...
Austin Merritt 7 months ago in Azure DevOps Services and Server  / Rally / Jira / Integrations 0 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...
Danny Archer about 1 year ago in Azure DevOps Services and Server 1 Future consideration