Add a new idea Subscribe
Status Shipped
Categories Azure DevOps Services and Server
Created by Andrew Keith
Created on Jan 21, 2016

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 RESPONSE
    Feb 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.
  • Attach files
  • Jeremy Lawson
    Reply
    |     Feb 14, 2018

    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?

  • Tom Gimpel
    Reply
    |     Nov 17, 2017

    Yes yes yes! 

  • Mark Neroni
    Reply
    |     May 18, 2017

    Did this ever get implemented?

  • Max Cascone
    Reply
    |     Jan 13, 2017

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

  • Bergen Helms
    Reply
    |     Nov 4, 2016

    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.

  • Andrew C
    Reply
    |     Mar 16, 2016

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

  • Ahmed Abdulmoniem
    Reply
    |     Feb 4, 2016

    Pretty important!

6 MERGED

Aha to VSTS Integration include State Reason

Merged
We'd like to see the VSTS State Reason come back into VSTS so we can see items that were reopened etc instead of just seeing the state alone
Guest about 7 years ago in Azure DevOps Services and Server 0 Shipped
6 MERGED

Ability to populate custom fields in TFS via Aha Integration

Merged
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...
Tony Lopez over 6 years ago in Azure DevOps Services and Server 0 Shipped
4 MERGED

Sync more data between Visual Studio and Aha!

Merged
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...
Ahmed Abdulmoniem over 6 years ago in Product 0 Shipped
4 MERGED

Map custom field data to export into VSTS

Merged
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...
Guest over 6 years ago in Azure DevOps Services and Server 0 Shipped