What is the challenge? ADO has released the ability to visualize deployment controls within an ADO record. In order to share this information with product management, this information needs to be able to sync back to Aha! via the ADO integration. ...
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...
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...
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...
Include history of comments when importing from ADO integration
What is the challenge?
Currently, when importing ADO records via an ADO integration only the latest comment is imported from ADO
What is the impact?
Inability to see comment history can lose critical context and require Aha! users to go to...
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...
Unable to map 'Assigned To User' of aha to 'Assigned To' field of ADO due is domain mismatch
What is the challenge?
Our organization has transitioned recently and so we got new domain for employees, currently both the domains are valid for employees. In few application like Aha! we have old domain itself, but in the new applications we ...
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...
Allow a single Azure DevOps webhook to support updates across multiple Aha! integrations
With Jira, a single Aha! webhook added at the system level supports updates across all Aha! integrations.
This makes scaling integrations simple as after the first setup, a user never has to add another webhook.
With Azure DevOps (TFS), each i...
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