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

  • Guest
  • Mar 29 2018
  • Future consideration
Release time frame
  • Attach files
  • Guest commented
    July 25, 2018 13:22

    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.

  • Tim Martel commented
    13 Aug 13:05

    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.