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.
|Release time frame|
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: