RELATED IDEAS
Map AHA data points into TFS
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 provide a separate option for mapping.
| Release time frame | 1 month |
-
ADMIN RESPONSEFeb 26, 2018
We have launched enhanced VSTS and TFS integrations. These integrations will allow you to map any Aha! standard or custom field to like fields in VSTS or TFS 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.
6
MERGED
6
MERGED
Ability to populate custom fields in TFS via Aha Integration
We have some custom fields in our TFS Work Item Types which are required, however those fields are not available in the Default feature fields drop down in Aha. We need the ability to set values for these custom TFS fields - even static values wou...
0
Shipped
4
MERGED
Sync more data between Visual Studio and Aha!
We need to sync more data between Aha! and VS like Story points and other stuff.
Currently, we can send default values into some fields in VS .. but it would be perfect if instead of passing a default value that I can pass a value of one of Aha! p...
0
Shipped
4
MERGED
Map custom field data to export into VSTS
It would be great to map custom field data to export into VSTS.
I have been able to map the custom fields with ideas to features and the data comes through when I promote the idea.
But when I export from Feature to Visual Studio Team Services it c...
0
Shipped
© 2025 Aha! Labs Inc.•All rights reserved
This would be incredibly valuable so as to not require manual double entry on some key fields we use for our Feature workflow and identification. Is there any indication when this will be implemented?
Yes yes yes!
Did this ever get implemented?
Yes, we need variables like this to be passed between integrations.
Very important. I am pretty disappointed that this does not come as standard feature till now.
Much manual work is required otherwise to shift over the feature content.
Especially for iteration assignment. Once we sync to TFS we have to manually go in and adjust the iteration assignment.
Pretty important!