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
  • Sean Elliott commented
    13 Feb, 2018 10:14pm

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

  • Admin
    Austin Merritt commented
    13 Feb, 2018 10:01pm

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

  • Derek Shehata commented
    13 Feb, 2018 05:53pm

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

  • Ahmed Abdulmoniem commented
    2 Dec, 2017 06:42am

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

  • Admin
    Chris Waters commented
    2 Dec, 2017 03:41am

    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.

  • Sean Elliott commented
    2 Dec, 2017 03:32am

    Chris, the link you shared returns "not authorized"

  • Max Cascone commented
    13 Jan, 2017 08:36pm

    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.

  • Ahmed Abdulmoniem commented
    4 Feb, 2016 12:43pm

    Sorry my last comment should be in another idea

  • Ahmed Abdulmoniem commented
    4 Feb, 2016 12:43pm

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

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

  • cami gui commented
    16 Oct, 2015 08:59am

    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.

  • +1