VSO integration: Allow custom fields to be mapped from Aha! to VSO

VSO integration: Allow custom fields to be mapped from Aha! to VSO
  • Chris Waters
  • Oct 15 2015
  • 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 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.
  • Attach files
  • cami gui commented
    October 16, 2015 08:59

    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.

  • Ahmed Abdulmoniem commented
    February 04, 2016 12:43

    No .. in VSO there is an option to do release which is Iteration.

    If we can map releases to iterations this would be perfect.

  • Ahmed Abdulmoniem commented
    February 04, 2016 12:43

    Sorry my last comment should be in another idea

  • Max Cascone commented
    January 13, 2017 20:36

    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.

  • Sean Elliott commented
    December 02, 2017 03:32

    Chris, the link you shared returns "not authorized"

  • Admin
    Chris Waters commented
    December 02, 2017 03:41

    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.

  • Ahmed Abdulmoniem commented
    December 02, 2017 06:42

    So Chris .. VS updates will not be available with the first rollout this month?

  • Derek Shehata commented
    13 Feb 17:53

    The support link provided above still shows up as "Not Authorized"

  • Admin
    Austin Merritt commented
    13 Feb 22:01

    Hi Derek, sorry about that. The article got removed but should be available now.

  • Sean Elliott commented
    13 Feb 22:14

    Any update on when this will be releasing?  what you are planning is exciting, but 6 months is a significant timeline with no specifics...?