RELATED IDEAS
Need full two way integration of a Story with VSTS
Right now you can push a Feature and associated stories to VSTS but if you delete a story in VSTS you have to manually delete in Aha. We need:
1) any story delete in VSTS to be automatically deleted in Aha
2) any story added in VSTS to a Feature that is linked to Aha to be automatically added to Aha associated with that same feature.
-
ADMIN RESPONSEFeb 26, 2018
Thank you for the request. In regards to deleting records across different tools, we make it a rule to never delete records between tools -- because this can cause very harmful unintended consequences (particularly when weighing this against the effort required to manually delete records).
In regards to the second component relating to adding VSTS stories to Aha! features, we have launched enhanced VSTS and TFS integrations that now makes this possible. You can now import newly created work items 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.
© 2025 Aha! Labs Inc.•All rights reserved
What if instead of deleting the VSTS entry, there was instead an option to set the VSTS entry to a certain state when the Aha entry was deleted. For example, a lot of the default templates for VSTS come with item states called "Removed" as a way to "delete without actually deleting". This seems like it would accomplish the original goal without the risk.