Skip to Main Content
ADD A NEW IDEA

Azure DevOps Services and Server

Showing 101 of 8645

Allow link of a requirement to a release (sprint)

We have features that are mapped to a specific sprint, but within that feature, we have requirements (user stories) that could be mapped to two different sprints. The assumption with Aha! is that a feature would be completed in one sprint, which i...
Guest about 1 year ago in Azure DevOps Services and Server 0 Future consideration

Add ability to sync custom table one to many field with AZURE DevOps Fields

I would like to be able to sync a one to many custom field, that links ties to a custom table, we have added to our requirements (PBIs), with the iteration path from DevOps. This does not appear to be possible. The reason for this is that we have ...
Jonathan Lewit over 3 years ago in Azure DevOps Services and Server 0 Future consideration

Add ability to transfer requirements between features and features between master features (epics)

If you take the typical hierarchy VSTS, of Epics, Features and Product Backlog items, its is great that with Integrations 2.0 we can map these to Master Features (we call these Epics), Features and Requirements (we call this PBI's). However we are...
Richard Harrison about 6 years ago in Azure DevOps Services and Server 0 Future consideration

Import of time tracker data from 7pace Timetracker to Aha!

7pace timetracker is an integrated time mamagement solution for teams using DevOps. We would like to pull time tracker data into Aha! through our DevOps integration to ensure Aha! has a clear view of the time spent on Features.
Guest almost 4 years ago in Azure DevOps Services and Server 0 Future consideration

Iteration Path Integration with Aha & ADO

Though we have Iteration path integration between Aha and ADO. This is currently limited to show dynamic values for the integrations. Also the Iteration Path is based on the Area Path, the values of Iteration path cannot be filtered / shown releva...
Raghuraman Rajendran over 1 year ago in Azure DevOps Services and Server 1 Already exists

Links to Azure DevOps items should be dynamically created based on integration settings

We underwent a branding change and had to update our Azure subdomain and after updating all our workspace integrations in Aha!, the hyperlinks (Azure DevOps Services url) were still pointing to the old subdomain and there is no way to refresh them...
Guest over 1 year ago in Azure DevOps Services and Server 0 Future consideration

Provide the ability to map the Release field from a Feature or Epic to an external system such as ADO

Given that AHA is all about releases and ADO is all about time lines, the concept of a Release in AHA is quite different than what exist in ADO - yet there is a Target Release field in ADO as well as in the Feature of AHA - please can this be expo...
Dirk K almost 3 years ago in Azure DevOps Services and Server 1 Future consideration

Filter capabilities on the Integration Update Import screen

As one Product Owner of a very large product that has a lot of product owners, I would like more filter capabilities on the Integration Updates import screen so that I can only see items that pertain to my portion of the backlog. This request is s...
Guest over 1 year ago in Azure DevOps Services and Server 0 Future consideration

Configure iterations based on phases in DevOps

We're using multiple layers of iterations within Azure DevOps. So a Release consists of multiple sprints. I would like to be able to map not only releases to iterations, but also phases to iterations. That way I can use Aha! as a single point of e...
Carlo Bril about 3 years ago in Azure DevOps Services and Server 0 Future consideration

ability to integrate idea information into Azure DevOps

We use the ideas portal to solicit new enhancements from our users and then link those ideas to features in our products. The problem is only our product management and dev management use Aha. our development team uses Microsoft DevOps to track th...
Joe Granville over 4 years ago in Azure DevOps Services and Server 0 Future consideration