Skip to Main Content
Status Shipped
Created by Guest
Created on Oct 13, 2015

How to integrate Releases to VSO

VSO does not have a good handle on representing releases. Can't really use the iteration mechanism, if your team is working on overlapping releases. Currently I'm using a highest level Feature in VSO to represent a release (or the Backlog) and then have a structure of Features below for organizing the work. Now that Epics are available maybe I'll look at using them for the release bucket. All this points to needing a flexible method for integrating Aha Release information into VSO. Whether your company has decided to represent release structure as Features or Epics or Iterations or whatever, the VSO Integration should accommodate.

    Feb 26, 2018

    We have launched enhanced VSTS and TFS integrations. These integrations will provide the option to sync releases with iterations in VSTS and TFS along with several other new capabilities including the ability to:

    • Set record mappings for Aha! initiatives, releases, master features, features, and requirements and link them to nearly any corresponding record type
    • Map default or custom fields in Aha! to any “like” field and specify which direction the updates should flow (e.g. from Aha! or from VSTS/TFS)
    • Automatically send outgoing changes from Aha! or choose to review and approve them
    • Import records directly from VSTS and TFS to make getting started in Aha! easy
    Check out the blog post for more details.
  • Attach files
  • Josh Wayne
    Jan 11, 2018

    I agree.  This is a challenge for us.  moreover, if I need to move a feature to a different release in Aha, I don't have a good way to update that in VSO

  • Karl Laird
    Aug 30, 2017

    This is a huge drawback of Aha at the moment - needing to go an manually stitch all the Features back together via an Epic after pushing through just creates missing deliveries and hamster work

  • Ahmed Abdulmoniem
    Feb 4, 2016


  • +1