Skip to Main Content
ADD A NEW IDEA

Azure DevOps Services and Server

Showing 89

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

Exportable list of orphaned workitems in Integrations update modal

Who would benefit? Aha admins, dev lead What impact would it make? Improved collaboration, minimizing integrations admin How should it work? Use case: I want to inform and support development team creating Azure Devops work items on Requirement le...
Mats Hultgren 6 months ago in Azure DevOps Services and Server 0 Future consideration

Integration to Azure DevOps for teams capacity planning

We would like to use Points based capacity planning but it needs to be integrated with (in our case) Azure DevOps which is where the team is committed to and working on work. All of our Features and Master Features (Epics) in Aha are calculated ba...
Heath McCarthy almost 4 years ago in Azure DevOps Services and Server 2 Future consideration

Function as a hub to push data from JIRA to DevOps

We use JIRA internally for tracking most of our development work, while a customer we work for uses DevOps. We also use Aha. We would like our customers to be able to see JIRA comments pushed through to DevOps. We tried to use Aha as a 'hub' to do...
Guest over 1 year ago in Azure DevOps Services and Server 2 Future consideration

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

Sync Release Phase to Azure DevOps

We have adopted a SAFe framework where features are planned quarterly. As a result we are creating 'Releases' in Aha that are materializing these quarters. Within a quarter we may deploy the software multiple times and we are using release phases ...
Nicolas Andrillon over 2 years ago in Azure DevOps Services and Server 0 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 5 years ago in Azure DevOps Services and Server 7 Future consideration

Allow linking of Features and Releases to a specific DevOps Iteration Level

We use a more granular structure to the Iterations in DevOps so mapping items to just the top level is not really suitable to keep a feature synchronized correctly and could involve a lot of manual changes at the beginning and end of a release. Fo...
Dave Ball almost 4 years ago in Azure DevOps Services and Server 2 Future consideration

Provide item ranking capability with Azure DevOps integration to Boards

Currently the Azure DevOps Boards integration does not include the capability to share the rank order of items in a workspace which results in the items in the Azure Devops Boards workflow having a different ordering than the items in the Aha rele...
Guest almost 3 years ago in Azure DevOps Services and Server 0 Future consideration

Allow mapping fields from related records in Aha to Azure Devops

This idea is to allow mapping fields from related records from Aha to DevOps. In most cases, this would be parent/grandparent/great grandparent situations. For example, allowing a tag from an Aha feature to be mapped to a tag on a DevOps PBI. Anot...
Josh Wayne over 2 years ago in Azure DevOps Services and Server 0 Future consideration