Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Azure DevOps Services and Server

Showing 118 of 9560

Support syncing of editing existing comments via ADO

What is the challenge? Editing existing comments in ADO do not sync back correctly in Aha! What is the impact? Comments can become out of date and not contain the correct information. Describe your idea Sync edits to existing comments
Stuart Blair 5 months ago in Azure DevOps Services and Server 0 Future consideration

Development Integration -- Support rendering of images embedded in description field

Currently when you import from Jira or Azure DevOps, if you have images embedded into the description field, they come over as a link in the Aha! description field, e.g. imagename.png. It would be great if they would render in Aha! like they do in...
Guest about 5 years ago in Azure DevOps Services and Server 9 Future consideration

Allow attachments to Feature comments to be integrated to Azure DevOps

When you add comments to a Feature, and you have integration with Azure DevOps (ADO) configured, you can have these comments passed back and forth. Unfortunately if you attach a file to a comment it will not get passed between Aha and ADO. When yo...
Guest over 4 years ago in Azure DevOps Services and Server 0 Future consideration

Add Markdown support for ADO integration

What is the challenge? Markdown editing has been added in Azure DevOps for rich text fields. However, when the data is migrated to Aha, it's stored as raw Markdown rather than displaying as formatted text. What is the impact? Makes integra...
Guest about 2 months ago in Azure DevOps Services and Server 0 Future consideration

Integrate ideas with ADO

What is the challenge? There is no easy way to send ideas to engineering to work on or keep the information in sync. What is the impact? Time spent copy and pasting data. Out-of-date information leading to confusion. Describe your idea Like the re...
Kelly Sebes 9 months ago in Azure DevOps Services and Server  / Ideas / Wanted 0 Future consideration

Bi-directional support for Area Level fields in ADO integration

What is the challenge? Currently we offer Area Level fields in our ADO integration for each Area Level. This allows us to receive the unique Area Level from ADO, but currently updates in Aha! do not change the Area Level back in ADO despite the se...
Stephanie Lechner 11 months ago in Azure DevOps Services and Server 0 Future consideration

Enable Roll-up Initiative link in the standard Azure DevOps Services integration

What is the challenge? Unable to integrate multi-layered strategic initiatives from Aha to ADO What is the impact? Manual updates to keep information in sync, prone to errors. Question whether we will continue to utilize Aha or work direct...
Guest 2 months ago in Azure DevOps Services and Server 0 Future consideration

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 7 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...
Guest 8 months ago in Azure DevOps Services and Server 0 Future consideration

Keep features in sync when they cross areas in Azure DevOps

This is useful when you have your DevOps areas configured by team. Once the features are pushed from Aha! to DevOps and evaluated by the team they need to be moved into the area for the appropriate team. Any team can work on any feature based on a...
Deb Gay about 6 years ago in Azure DevOps Services and Server 0 Future consideration