Azure DevOps Services and Server

What is the challenge? Each time I review Integration Updates I have to manually select the Workspaces, Integrations, and Record Types in varying levels to see the items needing to be addressed. Once I close out, and go back in later, I have to ...

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...

What is the challenge? Moving records within Aha! will no longer break integration links to ADO, however if records are moved within ADO the integrations links may break. In order for this to work, integrations need to be connected to the same ...

We are currently using Aha! Roadmaps and asking for consideration of implementing OAuth authentication when setting up the integration to Azure DevOps Services. With Microsoft making the push towards strengthening their customers security posture,...

What is the challenge? Currently, Aha integration with ADO syncs dependencies at Features level only. We need to also be able to sync the dependencies at Requirements/UserStories level.Including dependencies between Features and User Stories. What...

What is the challenge? When importing features from ADO the parent epic is automatically brought into Aha! Epics can live in separate projects and the team does not always want them to display within Aha! What is the impact? Difficulty in ...

What is the challenge? Dates added on AHA/ADO are not properly synced and show up on the other tool as +/- 1 day as a result of time differences between the two tools. Expected behaviour: When selecting a date in one tool, the same date appears in...

Who would benefit? Anyone who manages an Aha board that syncs with Azure DevOps (ADO) What impact would it make? It would reduce out-of-date information in Aha & on roadmaps from records that rely on the ADO integration for updates. Additional...

What is the challenge? Currently, when an Epic is changed to a Feature or vice versa in Azure DevOps (ADO), this change is not accurately synced with Aha!, leading to misalignment and inefficiencies. What is the impact? Epics and features are misa...

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. ...