Skip to Main Content
Status Likely to implement
Categories Jira
Created by Guest
Created on Mar 29, 2018

Ability to map JIRA Team-field to a custom field in AHA

In integration 1,0 it was possible to map JIRA team field to a customfield in AHA, but in the new 2.0 integration that is't possible

  • Attach files
  • Sophia Papadopoulos
    Oct 7, 2022

    Update from me and to hopefully help others - came up with a really hacky workaround.

    • Custom field in Aha - contains team names. Must be selected by Aha user on creation of ticket

    • Mapped to a custom field in Jira - this field is hidden on Jira tickets, but is associated with all tickets

    • Jira automation transforms the Jira custom field to the actual team name - using IF condition and EDIT FIELD action.

    I don't love the solution, it takes a lot of maintenance, but it works for now.

    In an ideal world, Aha would handle all of this and the mapping would include a sub mapping (like the status field) of team between Jira and Aha

  • Guest
    Oct 6, 2022

    We need this functionality to be able to properly plan our features by teams going into PI planning.

  • Kristina Kononiuk
    Sep 14, 2022

    This ability is very critical for us. I even don't know how to use the integration right now

  • Sophia Papadopoulos
    May 27, 2022

    Adding to this, we have exactly the same issue. Really critical for us to be able to implement this field in Aha.

    Would love to know how others have gotten around the issue?

  • Guest
    Mar 17, 2022

    Agreed that this is an essential feature...

    We have two development teams that will separately work on epics that are often then grouped together for a release. Thus, we need:

    • Team name to map between AHA and JIRA (as described)

    • To be able to filter by Team in AHA within the board, so that we can hold efficient / effective planning sessions at the team level within AHA

  • Michael Backhaus
    Oct 25, 2021

    The sync with JIRA Team field is critical for us since our Engineering department wants to have that field mandatory in JIRA. They want to avoid that Ideas/Feature Request are submitted to them without anybody feeling responsible for the implementation.

  • Tim Martel
    Aug 13, 2019

    Having this field available in Aha is critical.  Explanation is below.


    We use the Team field in JIRA to allow a product owner to submit a story to a service owner.  i.e. customer-facing product team needs infrastructure services, so they create the necessary story and assign to the proper service Team.  This then "moves" the story from the customer-facing team's board to the service team's board.


    We need this field to come over to Aha so that service owners have visibility into all of their responsibilities.  Without it, the service owners will only see stories that originated within their own service.  At least 50% of stories for service teams originate in other products.


    As the Team field is just another custom field, and verified to already exist within the JIRA API, please add it back to Aha as soon as possible.  Thank you.

  • Guest
    Jul 25, 2018

    Team/s in JIRA is used to identify which development group is needed to complete the epic, story or sub-task and as the Product Manager, I want to apply the same information in AHA so I dont have to do it in two places plus allows me to better understand the release capacity.

  • +1