Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Azure DevOps Services and Server

Showing 118

Support ADO multi-select dropdown

What is the challenge? Syncing multiple values between ADO <>Aha! requires support for the Multivalue control extension to work. Syncing editable choice lists works, pre-defined lists only sync 1 value when 2 or more are selected. What...
Tyler Carter 25 days ago in Azure DevOps Services and Server 0 Planning to implement

Add ability to map Created by Field between Aha! and ADO Server accounts

What is the challenge? Currently there are a few user fields from ADO server accounts available to map to Aha!'s Created by User, but the Created By user is not displaying as an option. What is the impact? Users are unable to map the created by fi...
Stephanie Lechner 6 months ago in Azure DevOps Services and Server 0 Future consideration

Allow use of Mapped fields template with one field difference for each integration

What is the challenge? Can't use Mapping Integration template. Have to update multiple integration for every mapping change since one has to be different. What is the impact? Would save a ton of time for our team. Describe your idea We have around...
Alex Berestenko 7 months ago in Azure DevOps Services and Server 0 Future consideration

Handle multi-select fields in ADO integration

What is the challenge? Running into an issue where multi-select from Aha can't flow over to ADO multi-select field. Only first value flows over from Aha. What is the impact? Can't use multi-select field in ADO properly. Describe your idea Allow fo...
Alex Berestenko 10 months ago in Azure DevOps Services and Server 0 Future consideration

Enable tags to be a selection for Azure DevOps integration of requirements

What is the challenge? You can sync tags for features but not requirements, What is the impact? creates duplication of work having to recreate tags in Azure DevOps Describe your idea As part of the field mapping for Azure DevOps integration "tags"...
Guest about 1 year ago in Azure DevOps Services and Server 0 Future consideration

Show name of user whose token is being used in ADO integration

Who would benefit? Admins of accounts with ADO integrations What impact would it make? When an ADO integration is created, a user with the correct permissions must enter their token to authenticate the integration. However, the token owner's name ...
Bonnie Trei almost 2 years ago in Azure DevOps Services and Server 0 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 2 years ago in Azure DevOps Services and Server 2 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 4 years ago in Azure DevOps Services and Server 0 Future consideration

Provide the ability to map the Release field from a Feature or Epic to an external system such as ADO

Given that AHA is all about releases and ADO is all about time lines, the concept of a Release in AHA is quite different than what exist in ADO - yet there is a Target Release field in ADO as well as in the Feature of AHA - please can this be expo...
Dirk K about 4 years ago in Azure DevOps Services and Server 1 Future consideration

Sync DevOps Commenter Name in Comment Sync

We are an outsourced product management company, so we have alot of integrations to alot of our customers. We have found that when an individual in one of our customers orgs makes a comment, the comment text is sync'd, but the name of the person w...
Guest over 4 years ago in Azure DevOps Services and Server 0 Future consideration