Add a new idea Subscribe
Status Shipped
Categories Integrations
Created by Ron Yang
Created on Dec 14, 2016

RELATED IDEAS

Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit APP-I-2828 Rally integration: Add support for custom field integration mappings for two-way custom field updates.

Sync custom fields at the requirement level with Rally and TFS Merged

Aha! currently allows custom fields on requirements. It should be possible to sync requirements custom fields data with dev systems linked to Aha! 

Admin note: This capability was shipped for the JIRA integration. Updates to the Rally and TFS integrations are also planned

  • Kaitlyn Moore
    Reply
    |     Jun 2, 2017

    Do we know when this will be coming out?  Our management is considering killing our Aha subscription because so many of our VSO fields are out-of-sync with Aha, most notably, Release<-> Iteration path, assigned to, and priority.

  • Rob Oesch
    Reply
    |     Feb 8, 2017

    Looking forward to the TFS Integration for this.  Thank you for a great product!

  • Ron Yang
    Reply
    |     Feb 2, 2017

    Hi - we just pushed an update this morning to the JIRA integration, allowing you to sync custom fields at the requirement level. In your JIRA configuration settings page, you'll see a new section for Requirement field mapping which will allow you to do so.

    We will post an update to the support documentation here shortly.

    In the meantime, we will set this Idea back to "planned" to account for the upcoming updates to the TFS and Rally capabilities.

  • Zac Coleman
    Reply
    |     Feb 2, 2017

    I see this is now marked as shipped, but I am still not able to get this configured with my integration. Am I too soon and need to wait for deployment? 

  • Zac Coleman
    Reply
    |     Jan 30, 2017

    Agreed! We would use this day 1. 

  • Shri Iyer
    Reply
    |     Dec 18, 2016

    This feature is desperately needed. Currently we are having to manually sync up the field values between Aha and JIRA which is extremely time consuming.

  • Charles Evans
    Reply
    |     Dec 14, 2016

    I was very excited about the custom fields  at the requirement level being shipped.  Without this feature, however, it won't help us with what we're trying to achieve.

  • Guest
    Reply
    |     Dec 14, 2016

    Yes, please, as soon as possible. This is the missing link (no . . . ok, pun intended). By sending this into JIRA, teams can key off a custom field as a constant for a team to pull items into their Agile boards, and product can toggle this field from Aha as a control point to assign into those Jira boards.