Ability to link features/requirements to existing VSO work items
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
We're using Aha with Azure DevOps integration. We’ve mapped the Estimate field in Aha with an estimate field in Azure DevOps.
Our estimation process is basically as follows:
* Product Manager creates Feature in Aha
* Product Manager send RFC...
Support Azure DevOps integrations for parent and child records across workspaces
What is the challenge? When a parent or a child record is moved to another workspace in Aha! it will no longer update via integrations due to the child and parent existing in different workspaces in Aha! What is the impact? Integrations break when...
As a product manager, I should have control over the destination of where imported features and epics go so that they are in the release or parking lot where they belong. Today, the destination of imported items seems almost up to chance although ...
Right now you can only define default values for TFS fields. It would be better if there was a way to map fields in AHA to fields in TFS, including custom fields. This could be done by using variables (aka: {{Assignee}}) in the current UI or provi...
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!