Azure DevOps Services and Server

Current VSO/TFS integration only allow to submit a feature/requirement from Aha! to TFS/VSOAn option to link a feature/requirement with an existing TFS/VSO work item would be helpful

VSO integration: Allow custom fields to be mapped from Aha! 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 the...

If a feature has been sent to TFS as a feature and requirements as stories, when I create a new story under the linked feature I would like it to be automatically created in Aha! as a requirement.

The integration with TFS has a lot of potential, but it's still work to have to remember to click the Action then Update TFS. If some product owners forget, then we have to audit what features and requirements are in both systems and see which one...

It would be great if we could have Initiatives sync over to TFS as Initiatives or Epics to get the full hierarchy tracked in both systems. As it stands, we have to manually create initiatives in TFS and then link the Features up to them. Adding it...

Epics on top of feature were introduced with VSO a few weeks ago. The VSO Connector should be able to reflect that somehow. Either by also working with epics in aha that encapsulate features or better the easy MVP way with a global setting for the...

Whilst the integration between Aha! and VSO (Visual Studio Online) is a great start, I feel (and have experienced a need) that there can be further collaborative integration between the 2 platforms. My thinking is that it would be great to integra...

Integration with TFS 2015 on prem which includes the Rest API: https://www.visualstudio.com/en-us/news/tfs2015-vs.aspx#restapi This is the first release that brings REST APIs to on-premises TFS.