RELATED IDEAS
Status sync between AHA and VSO
Given that a PM controls their backlog and roadmap from AHA it would make sense for them to be able to do more than simply send the story to VSO and be subject to changes that are prompted only from VSO to AHA.
For example, if i decide that a feature should no longer be implemented, I want the feature to be removed from the VSO backlog if i set the status in AHA towill not implement (considering this is a matched status). It makes sense because VSO is the space for development and AHA is the space for product management and the decision flow should be adapted accordingly.
-
ADMIN RESPONSEFeb 26, 2018
We have launched enhanced VSTS and TFS integrations. These integrations provide the option to setup a 2-way status sync along with several other new capabilities including the ability to:
- Set record mappings for Aha! initiatives, releases, master features, features, and requirements and link them to nearly any corresponding record type
- Map default or custom fields in Aha! to any “like” field and specify which direction the updates should flow (e.g. from Aha! or from VSTS/TFS)
- Automatically send outgoing changes from Aha! or choose to review and approve them
- Import records directly from VSTS and TFS to make getting started in Aha! easy
Check out the blog post for more details.
© 2024 Aha! Labs Inc.•All rights reserved