Azure DevOps Services and Server

For Project Status, currently the only information we have is feature and requirement status coming from Aha to VSO / VSTS and vice versa. It would be far better for businesses tracking effort to be able to put estimates into either tool synchroni...

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.

We spend all that time estimating and have to reproduce the work when we send the stories to TFS. Please! Make it stop! Setting to a month because this seems like a no-brainer!

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...

For successful product management and development, User Stories and Acceptance Criteria are key. We want our Product Owners defining not only the user story (requirement) but also the associated acceptance criteria within Aha!. This information wo...

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...

VSO integration: Allow custom fields to be mapped from Aha! to VSO

It would be useful if Aha allowed for mapping of Master Features the same way it allows Features to be mapped.

Aha! integration with TFS should create a hyperlink in the TFS item when the Send to Team Foundation Server action is selected and a new TFS item is created. Additionally, an action that sends a link record to TFS would be helpful if the link is l...