Skip to Main Content
ADD A NEW IDEA

Azure DevOps Services and Server

Showing 108

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 about 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 about 4 years ago in Azure DevOps Services and Server 0 Already exists

Aha! Releases Should Honor ADO Area by Default

I am unsure why this feature was designed this way; However, when creating and pushing a release from Aha! to ADO, it should honor the area path set up in the Aha! to ADO integration. Furthermore, when linking to an existing iteration in ADO, the ...
I R over 1 year 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

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 over 6 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

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

Allow mapping Release as a field on Requirements in Azure DevOps integration

Due to our iterations setup in Azure DevOps (ADO) we do not currently map Releases as a record. We are sending this instead as a field on the Epic and Feature records to a custom field in ADO. We would like to do the same on Requirements but it is...
Guest about 3 years ago in Azure DevOps Services and Server 0 Future consideration

Limit workspace users choice to 1 user instead of multiple (like the Assigned to) field

I need to add the workspace users as a custom field in my template and currently it doesn't limit to just one user, it allows multiple users which I cannot have. Can we have an option to make it a single choice only. in the attached graphic is the...
Stacy Monnahan about 2 years ago in Azure DevOps Services and Server 0 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