Skip to Main Content
Status Shipped
Created by Ben Snapper
Created on Jun 3, 2020

Dependency record links available as part of the Azure DevOps integration

I understand you've created the dependency link in Aha! with Jira, it would be great to have this in ADO (Azure DevOps) too please

    Sep 2, 2021

    Dependency syncing is here for the Aha! Roadmaps and Azure DevOps integration. You can now map record links in Aha! with work item links in Azure DevOps — so everyone can instantly see the work that impacts their plans.

    If you already have an integration with Azure DevOps, go to the Mappings step, click "Reload configuration", then add a field mapping for Aha! record links <-> Azure DevOps related work.

    Learn more.

  • Attach files
  • Diana Ramchandani
    Aug 12, 2021

    I second all the comments below, it would really help improve the efficiency with which we manage product backlogs and maintain traceability across requirements. We already benefit from the integration in terms of mapping tech tasks in ADO to features originating in Aha!, so it would be much appreciated if we could use this fully to enable ADO to pick up any feature dependencies/links from Aha!

  • Casey H
    May 19, 2021

    Aha! currently only allows Feature-level dependency mapping, and those do not map to the dependency settings within Azure DevOps.

    Requiring duplicate work from our POs to set dependencies in both ADO and Aha increases the administrative effort to use Aha and diminishes the value Aha provides as our potential go-to planning and collaboration tool for cross-team roadmapping and collaboration functionality.

  • Rachel Fitton
    Mar 3, 2021

    Aha has seriously improved efficiency within our product management community when it comes to prioritisation and roadmapping. The need to manually link records however both in Aha and AzDO as this is not available within the integration, means that the product manager still has to work in AzDO rather than focusing solely in Aha and is proves an overhead, causing frustration which casts a shadow on the otherwise amazing Aha experience.

  • Guest
    Oct 28, 2020

    +1 Please add this feature.

  • Guest
    Aug 25, 2020

    Agreed, no one wants to have to do duplicate work for the same information and or worry about the systems not being in sync. Thanks!!! This is especially important for our functional teams like Architecture and DevOps that multiple areas are dependent upon to create and add visibility to that dependency.

  • Aaron Wiebe
    Aug 25, 2020

    YES PLEASE. Doing this twice or having to only represent dependencies in one of the tools is not ideal.

  • Guest
    Aug 12, 2020

    This would be a game changer for Agile team, our company and our teams as most of the work we do is dependent on multiple teams to execute. This would be a fantastic feature to have an will upgrade the value of Aha! as a lot of organizations are using ADO and their road-mapping capabilities are limited. This also means, that we can bring our planning teams and will definitely increase the number of licenses needed moving forward which will be a good value proposition for Aha!

  • DeMarkus Wilson
    Aug 10, 2020

    This would seriously be a game changer. Right now my company is looking at Aha! strictly for PI planning and the Gantt feature which lets you easily visualize dependencies across teams.

    ADO has a feature called "dependency tracker" which looks the same but is not nearly as user friendly. If Aha! were to develop the record links for dependencies I could see Microsoft recommending it as the premier go to tool for PI Planning w/ADO. They would likely abandon "Dependency Tracker" all together and tell users to link dependencies first in Aha! then drag them into ADO voila' :)

  • Guest
    Jun 23, 2020

    I would love this. It would be great to know when a dependency is created by Aha showing the update for me as opposed to having to manually associate features.

  • Hannah Wardrop
    Jun 22, 2020

    This is something that we require. It's currently a barrier to purchase as it's an essential part of our planning. Are there any decent work arounds which don't require duplication of data entry in DevOps and Aha! ?

  • Matt Thomson
    Jun 8, 2020

    Agree this would be really useful - for example we often have bugs that are raised directly in Azure Devops by QA, and they can require some investigation tasks (a separate work item). Right now there's no easy way to map that dependency of Investigation -> Bug across to Aha, besides using a standard naming convention, but that's really only useful if the two work items are close to one another in the backlog

  • +2

Link related items (i.e. dependencies) in VSTS integrations

Dependencies (and other relationships) between Features, Epics are important in VSTS for developer info. As far as I can see, 'related items' integration exists for JIRA but not VSTS?
Tom Wilsher over 1 year ago in Azure DevOps Services and Server 0 Shipped