Skip to Main Content
ADD A NEW IDEA

Azure DevOps Services and Server

Showing 103 of 8729

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 almost 6 years ago in Azure DevOps Services and Server 3 Future consideration

Nested Iteration Paths with VSO / Visual studio team services integration

We have the same VSO project for many products in Aha. We would like the ability to have child iterations for releases so we can group them together in our queries. Current integration only allows us to go 1 level deep in the iteration path. Our...
Josh Wayne about 6 years ago in Azure DevOps Services and Server 0 Already exists

TFS Integration, match user for "assigned to" field

Aha! takes my email address as user name but TFS requires <DOMAIN>\<Last Name> as user name. Therefore the integration throws errors when an Aha! user is set in the TFS "Assigned to" field of a feature. My suggestion to solve this is t...
Guest about 6 years ago in Azure DevOps Services and Server 3 Unlikely to implement

VSTS updating Aha! features base user stories

Leadership and executives are using Aha! more and more. Having the ability to represent the percentage completed of features in a given release is very important when reporting to large audience. I like to ability to show the percentage of the Fe...
Guest about 6 years ago in Azure DevOps Services and Server 0 Already exists

Control how Estimates are converted and sent to TFS/VSTS

The default behaviour of how the TFS/VSTS integration sends time Estimates in minutes is very limiting. I don't know any agile team that would be estimating Features or Requirements down to minutes, so it doesn't make sense for the integration to ...
Guest about 6 years ago in Azure DevOps Services and Server 1 Future consideration

Ability to search for key words in Integration updates when importing new records

After the updated TFS integration which allows records to be imported directly from TFS into Aha. It would be ideal to be able to search the new record list for key words. Currently you can filter the list but this is not very user friendly and if...
Guest about 6 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 over 6 years ago in Azure DevOps Services and Server 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 ...
Tom Beck over 6 years ago in Azure DevOps Services and Server 9 Future consideration

Automate service account password updates for TFS integrations

Right now we have a TFS integration configured with Aha which requires us to use an AD service account for TFS. This service account password needs to be manually added within Aha! however we have a policy that all our service accounts require pas...
Jeremy Lawson over 6 years ago in Azure DevOps Services and Server 0 Unlikely to implement

Would it be possible to not need a paid AHA account to process VSTS updates?

At the moment we have set up the VSTS integration with a paid AHA account as required. This means that all updates come in from that product manager. In the history threads, and the notification emails we get a combination of VSTS updates, and the...
Guest over 7 years ago in Azure DevOps Services and Server 1 Unlikely to implement