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. 

  • Andrew Keith
  • Jan 21 2016
  • Shipped
Release time frame 1 month
  • Feb 26, 2018

    Admin Response

    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.
  • Attach files
  • Ahmed Abdulmoniem commented
    February 04, 2016 12:39

    Pretty important!

  • Guest commented
    March 16, 2016 12:53

    Especially for iteration assignment.  Once we sync to TFS we have to manually go in and adjust the iteration assignment.

  • Bergen Helms commented
    November 04, 2016 06:59

    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.

  • Max Cascone commented
    January 13, 2017 20:34

    Yes, we need variables like this to be passed between integrations.

  • Mark Neroni commented
    May 18, 2017 19:16

    Did this ever get implemented?

  • Tom Gimpel commented
    November 17, 2017 16:06

    Yes yes yes! 

  • Jeremy Lawson commented
    February 14, 2018 23:09

    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?