Skip to Main Content
ADD A NEW IDEA

FILTER BY CATEGORY

Azure DevOps Services and Server

Showing 87

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

New features created via an ADO integration are assigned to the parent epic release by default

Key problem: the "Parent" field in ADO can contain only one value. In ADO, a feature is automatically associated to the same theme as its' parent epic, but in Aha! this is not the case. So when features import, we associate them with the correct p...
Bryan McElhinney 5 months ago in Azure DevOps Services and Server 0 Future consideration

Add support to map Azure Boolean Fields to Aha

This request is to support the mapping of ADO boolean fields to Aha predefined droplist and tag fields. Currently, Azure DevOps Boolean fields (true/false) cannot be mapped to Aha fields. Rather, in ADO, you need to create a field as a picklist in...
Jerrold Emery about 1 year ago in Azure DevOps Services and Server 0 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 over 1 year ago in Azure DevOps Services and Server 0 Future consideration

Aha! Azure DevOps Integration Community

Is anyone interested in starting up a Aha! Azure DevOps Integration Community to share ideas, best practices, discussions on how you solved complex integration problems.
Deb kelchner almost 2 years ago in Azure DevOps Services and Server 0 Future consideration

Map persona record in ADO integration

No description provided
Guest about 2 years ago in Azure DevOps Services and Server 0 Future consideration

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 about 2 years ago in Azure DevOps Services and Server 0 Future consideration

Properly transfer images in VSTS comments to Aha!

Currently, if a user adds a comment to a User Story or Bug discussion in VSTS and embeds an image in the comment, the image doesn't come through with the comment that shows up in Aha!. This makes it difficult for the reader in Aha! to follow the d...
Guest about 4 years ago in Azure DevOps Services and Server 0 Future consideration