Skip to Main Content
Status Shipped
Categories Jira
Created by Guest
Created on Nov 11, 2014

Ability to map standard fields in Aha to custom fields in JIRA

It would be really useful if I could map standard fields in Aha to custom fields in JIRA. For example...

- Assigned User to Product Owner

- Aha Score to Business Value

These are fields that we use in JIRA that we are having to manually type in again. Would be a great enhancement to have this flexibility.

    Dec 14, 2017

    We have launched an enhanced Jira integration. This integration will allow you to map default fields in Aha! with any like field in Jira, 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 Jira)
    • Automatically send outgoing changes from Aha! or choose to review and approve them
    • Import records directly from Jira to make getting started in Aha! easy
    Check out the blog post for more details.
  • Attach files
  • Guest
    Aug 10, 2017

    This is much needed

  • Mike Eng
    Nov 28, 2016

    +1 for some way to bring Aha Score into Jira

  • Sudipta Panda
    Nov 24, 2016

    We too want the same functionality. Mapping any field from JIRA to any field at Aha with same data type. Once of the Aha! representative mentioned we can not map JIRA field which is object type to Aha! towards my request to map Epic Name in JIRA to a custom field (Text Type). What was expected that the Epic Name is a text what we see in JIRA and should be able to map to Aha!'s any text custom field.


    Basically the non custom fields are not appearing for mapping for both JIRA and Aha! which is essential to model the integration.



    SAP Ariba

  • Guest
    Sep 13, 2016

    We have Aha Features linked to Epics in JIRA.  I'd like to be able to map the initiatives field of a feature in Aha to a custom field in JIRA for the epic (so I can see in JIRA which initiative an epic belongs to).

  • Michael Morrison
    Jul 21, 2016

    Similar need - We use a custom field in JIRA for story points; we would need the ability to map that to the standard AHA Estimate field.

  • Michael Morrison
    Jul 11, 2016

    Similar need - We have a custom field in JIRA to track story points, i'd like to map that to Estimates (standard field) in Aha!

  • Rob Ormond
    Feb 4, 2016

    This would also be extremely useful to us.  Most people in our business refer to the new features by their Aha! feature number.  This is exported to JIRA in the Aha! Reference field, but it is a whole URL back to Aha!  We would ideally like this to be a custom field that holds just the feature number (xxx-nnn) so we can easily make that visible in JIRA to avoid confusion about which JIRA story relates to which Aha! feature

  • John De Goes
    Sep 3, 2015

    This is very important to minimize the amount of manual fiddling that a product developer must perform after exporting data into JIRA.


    I would prefer full generality: that is, all of the dimensions listed on the pivot table should be capable of being mapped into JIRA fields, and visa versa. Note that some JIRA fields are actually *lists*, such as Component: an issue may affect multiple Components. Whereas a corresponding source field in Aha! may be constrained to a single value. In any such 1-to-many mapping, if true synchronization is being performed, then the Aha! field value should not be overwritten *unless* the target (list) field in JIRA does not contain the Aha! value.


    If a fully general solution is not possible, my main pain is around preserving the full hierarchy in JIRA.


    In particular, the JIRA hierarchy maps to the Aha! hierarchy in the following way:


    • JIRA Component -> Aha! Goal
    • JIRA Epic / Parent Task -> Aha! Initiative
    • JIRA Issue / Subtask -> Aha! Feature
    • JIRA Subtask -> Aha! Requirement


    Currently, only *part* of this hierarchy is preserved. The rest is discarded, resulting in the loss of important information.


    My #1 goal in such a feature would be preserving the hierarchy in a fashion that is as natural as possible to JIRA / JIRA Agile users.

  • Guest
    Apr 23, 2015

    This is something that we really want. At comScore, PM are not responsible for managing or creating releases. We PMs create projects in Aha (releases) and export them to Jira. The releases are  managed in Jira using the Fix Version field by Release Managers. 

    As a Product Manager I would like to see all the Aha features (across all my releases/projects) that are going to be released in Release X. This means that I should be able to filter the Feature Board based on custom Aha field that is mapped to the Fix Version field in Jira.

  • Guest
    Jan 28, 2015

    This feature would be great


More flexibility in Mapping Initiatives with JIRA

I;d like the option for Aha Initiatives to appear in JIRA as fields in an JIRA issue. Our company does not use JIRA sub-tasks for Feature requirements. We use sub-tasks for tasks needed to deliver the requirements--engineering tasks, QA tasks, etc...
Guest over 8 years ago in Jira 0 Shipped