Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Azure DevOps Services and Server

Showing 117

Calculate remaining effort based on detailed estimate and work done

What is the challenge? When adding a detailed estimate in Aha! or ADO and then logging actual effort via ADO, the Actual effort remaining value does not change and the progress bar total is inaccurate. Add initial estimate in aha! Send to ADO. Add...
Stuart Blair over 1 year ago in Azure DevOps Services and Server 2 Future consideration

Receive an email notification when something is in the "integration updates" tab ready to import

What is the challenge? As we do not use releases for some workspaces not everything pulls in automatically, so there are things in the integration updates tab that we don't know are there until we check it. What is the impact? Sometimes we...
Megan Davis about 1 month 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...
Mike Maylone 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 almost 5 years ago in Azure DevOps Services and Server 0 Future consideration

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 7 months ago in Azure DevOps Services and Server 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 about 1 year 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 12 months ago in Azure DevOps Services and Server  / Ideas / Wanted 0 Future consideration

When Sending Whiteboards to Integrated Devops, Send as image, not link

What is the challenge? When a Whiteboard is included within a feature that is sent to DevOps (and I assume Jira), a link is sent, not an image. What is the impact? Many, if not all users in DevOps do not get access to Aha Describe your...
Steve C 3 months ago in Azure DevOps Services and Server 0 Future consideration

Map VSTS/TFS picklist custom fields to Aha! choice list fields

VSTS/TFS picklist custom fields are treated as strings and cannot support option mappings. Mapping a picklist field to an Aha! choice list field should provide the option to click Configure and map the choices.
Tessa Adair over 6 years ago in Azure DevOps Services and Server 9 Future consideration

DevOps Integration: Sync "Task" Workitems with Aha's "To-Dos"

Currently, our main work in DevOps gets done within Task items which also have effort spent inside. These however are not a sync-option within the "To-Do" level of Aha!. The fields "Name, Description, Assigned to, Due Date (and maybe effort or oth...
Michael Scholze almost 5 years ago in Azure DevOps Services and Server 1 Future consideration