Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with

We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.

  • Kevin Konishi
  • Apr 13 2016
  • Already exists
  • Jun 16, 2016

    Admin response

    The best way to achieve this today is to would be to configure multiple JIRA integrations. Each integration would be separately linked to Epics, stories or bugs. 

    By putting this in place, this would allow you to create features and defects in Aha! and designate them in JIRA based on the issue type of interest.

  • Attach files
  • Rob Parrish commented
    24 Aug, 2017 07:59pm

    Same issue. This doesn't already exist, though i understand the work around.

    For example, lack of this capability prevents me from pushing a whole release at once to JIRA. As that release can include both bugs and story & and improvement tickets. All of which must be sync'd separately.

  • Steve T commented
    24 Apr, 2017 05:33pm

    I typed a lot and now your login process has deleted all my comments.


    The same with this issue, I just want it to map over everything I dont need additional headaches, they serve no purpose. Thank you

  • Steve T commented
    24 Apr, 2017 05:32pm

    I see no benefit on explcit mapping except more headache. When I click on Actions -> Link to JIRA I need to map to whatever issue type we ever defined in JIRA and or default issue types. 

  • Max Cascone commented
    9 Feb, 2017 05:58pm

    I have the same issue with the VSTS integration. Without a separate Bug type in the Aha schema, or ideally, a separate category in the Integration configuration for Bugs, you'd need to create a specific integration for Bugs that map Aha Features to VSTS (or Jira) Bugs.

  • Jacob Bockelmann commented
    11 Jan, 2017 06:02am

    Ditto to Heather and Marc. This feature doesn't already exist and if your work around is to create multiple Jira integrations you should provide instructions for how to do so.

  • Heather Read commented
    2 Dec, 2016 06:03pm

    So for this to work we have to install a JIRA integration for each Feature type? Can you provide some specific instructions on how the rest of the integration template should be filled out relating to the auto-import fields so we can implement the set up correctly?

  • Guest commented
    16 Jun, 2016 03:58pm

    This is something we desire also. Please remove the "Already Exists" label because that's not accurate and will garner it less attention.

  • Todd D. commented
    20 Apr, 2016 12:19pm

    Same thought as Kevin - an Idea that comes in may be a bug or a one line change, or it may be "epic-big".  Having the ability to "Send to JIRA as..." and allowing the user to specify an Issue Type would be hugely helpful, even if it can only populate the shared fields.

  • Kevin Konishi commented
    13 Apr, 2016 09:21pm

    Sorry here is the file

  • Kevin Konishi commented
    13 Apr, 2016 09:19pm

    You misunderstood, look at the attached file.  For the "Feature" issue type it can only be mapped to one JIRA issue type, I need to be able to map to one or more.