RELATED IDEAS
Sync Initiatives with TFS
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 to the integration would save time.
-
ADMIN RESPONSEFeb 26, 2018
We have launched enhanced VSTS and TFS integrations. These integrations will allow you to map Aha! initiatives 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.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
22
MERGED
Map Aha! initiatives to epics in TFS
As currently implemented, we have to manually map the features we send to TFS to the corresponding epics. The duplication of effort risks missing features or introducing errors, between the two platforms. Putting timeline as quarter because we're ...
5
Shipped
© 2024 Aha! Labs Inc.•All rights reserved
Agree. this is a primary reason we have not integrated.
Agreed.. the Aha product feels too isolated without fuller bi-directional integration - that includes epics, features, PBI/Stories, etc
Also very important and a good third step to making this a useful integration. A full featured integration would need to include the option to control which Aha fields get mapped to which VSO fields and whether they get pushed both directions.