VSO integration: Allow custom fields to be mapped from Aha! to VSO
VSO integration: Allow custom fields to be mapped from Aha! to VSO
| Release time frame | 1 month |
-
ADMIN RESPONSEFeb 26, 2018
We have launched enhanced VSTS and TFS integrations. These integrations will allow you to map custom fields 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
11
MERGED
VSO/TFS map custom field or field to VSO Field
Provide the ability to map a aha custom field or standard field to a VSO Field.
For example I have a field for Acceptance Criteria in Aha. I would like to map this to the Acceptance Criteria on VSO. So that when i push the content across the conte...
2
Shipped
© 2025 Aha! Labs Inc.•All rights reserved
Any update on when this will be releasing? what you are planning is exciting, but 6 months is a significant timeline with no specifics...?
Hi Derek, sorry about that. The article got removed but should be available now.
The support link provided above still shows up as "Not Authorized"
So Chris .. VS updates will not be available with the first rollout this month?
Sorry, it got moved to an private part of our support site. I have moved it back and published it again, so it will be visible now.
Chris, the link you shared returns "not authorized"
Right now I've created a custom field in VSTS for the Aha ID. I can't automatically populate this with the Aha ID without a variable being passed in through the integration (voted on another idea that wants this).
So either allow custom fields to be mapped AND variables passed through the integration, or automatically add a link in the VSTS item back to the Aha item.
Sorry my last comment should be in another idea
No .. in VSO there is an option to do release which is Iteration.
If we can map releases to iterations this would be perfect.
Whatever business flow we decide to opt for in VSO, we need to always have its equivalent in AHA. Business value is the first to start with.