Some customers have specified that they maintain a single VSO Project, but represent a number of products beneath it. The way to handle that now in Aha is to set up a web-hook for each product in Aha, and then create a subscription in VSO that filters based on the area path. Perhaps we can set up a more streamlined way to handle these integrations with VSO on the Aha end?
Given the current capability of setting up multiple integrations in Aha! and corresponding service hooks in VSTS and TFS, we are unlikely to implement this idea at this time.