Skip to Main Content
Status Shipped
Created by Chris Waters
Created on Oct 15, 2015

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

VSO integration: Allow custom fields to be mapped from Aha! to VSO
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 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
  • Guest
    Reply
    |
    Feb 13, 2018

    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
    Reply
    |
    Feb 13, 2018

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

  • Derek Shehata
    Reply
    |
    Feb 13, 2018

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

  • Ahmed Abdulmoniem
    Reply
    |
    Dec 2, 2017

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

  • Admin
    Chris Waters
    Reply
    |
    Dec 2, 2017

    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.

  • Guest
    Reply
    |
    Dec 2, 2017

    Chris, the link you shared returns "not authorized"

  • Max Cascone
    Reply
    |
    Jan 13, 2017

    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
    Reply
    |
    Feb 4, 2016

    Sorry my last comment should be in another idea

  • Ahmed Abdulmoniem
    Reply
    |
    Feb 4, 2016

    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
    Reply
    |
    Oct 16, 2015

    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
11 MERGED

VSO/TFS map custom field or field to VSO Field

Merged
Provide the ability to map a aha custom field or standard field to a VSO Field. For example I have a field for Acceptance Criteria in Aha. I would like to map this to the Acceptance Criteria on VSO. So that when i push the content across the cont...
Guest over 8 years ago in Azure DevOps Services and Server 2 Shipped