Skip to Main Content
ADD A NEW IDEA

Azure DevOps Services and Server

Showing 108

Update records selectively

The "Update Records" feature currently updates all integrated records defined in the Azure DevOps integration. This could take quite some time if the number of records is high. Sometimes you only want to upgrade on a particular record type because...
Guest almost 4 years ago in Azure DevOps Services and Server 0 Future consideration

Sync sprints between requirements in Aha! and equivalent (e.g. PBIs) in Azure DevOps

Our development team manages PBIs within sprints. Currently you can map a custom sprint field for features in Aha! to DevOps, but not requirements. Ideally, we would be able to sync sprints for requirements/PBIs, as that would be more useful than ...
Mike Maylone over 4 years ago in Azure DevOps Services and Server 0 Future consideration

Comment Synching to Azure DevOps

As an Aha user, when I create a Requirement with a Comment which is mapped to Azure DevOps I need the initial Comment to synch to Azure and not just subsequent Comments Working with offshore teams, and not able to speak to them during off hours, w...
Lee-Ann Ruf over 4 years ago in Azure DevOps Services and Server 0 Already exists

Ability to customize the Import Import New Records dialog box and functionality

It would be very helpful to be able to customize and configure the Import New Records dialog box. Specifically I would like to be able to select additional/different information about each record (i.e. Azure DevOps work item #, State, Iteration) i...
cheryl fetchko about 5 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

Update the Feature % Complete field based on User Stories of the DevOps Feature

Update the Feature % Complete field based on User Stories of the DevOps Feature that is linked to the Aha Feature. The Software Product Plan does just that! In DevOps, this information is a calculated field, which can be easily configured in Board...
Guest almost 2 years ago in Azure DevOps Services and Server 2 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 almost 3 years ago in Azure DevOps Services and Server 0 Future consideration

Allow two-way integration for picklist fields in Azure DevOps when using the XML process model

This idea is a variation on https://big.ideas.aha.io/ideas/AFME-I-2, but the general use case is the same. I've been asked by Aha support to make a separate idea specifically for those using the XML process model, since this has supposedly been fi...
Tessa Adair over 3 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 over 4 years ago in Azure DevOps Services and Server 1 Future consideration

Azure DevOps integration support for designating default Iteration as backlog

Currently the Azure DevOps Services integration supports configuration of the project and the project area. All work items go to the root project iteration level. However, multiple teams may work in a single project and have a different iteration ...
Ronnie Merkel over 4 years ago in Azure DevOps Services and Server 2 Future consideration