Skip to Main Content

Share your product feedback

When creating feature and selecting feature type "bug" creates issue in Jira as "story"

This is really important to be able to map these when creating new features in releases for me.  

  • ADMIN RESPONSE
    Feb 18, 2016

    We currently have the flexibility to indicate which feature types will create issues in JIRA.

    In the JIRA settings page, you can click the "Only auto import mapped issue types" to only send the issues types which you have mapped between Aha! and JIRA. Unchecking this box will allow all issue types to be sent to and from JIRA.

  • Attach files
      Drop here to upload
    • Admin
      Austin Merritt
      Reply
      |
      Oct 13, 2017

      Yes that is correct. You will just want to use a single webhook. 

    • Max Cascone
      Reply
      |
      Oct 13, 2017

      In this case I’m matching the exact use case described in https://support.aha.io/hc/en-us/articles/215190823-When-to-use-multiple-JIRA-integrations-for-a-single-product - i have an integration set up for Bugs, and another for everything else. Do they both use the same webhook?

    • Admin
      Austin Merritt
      Reply
      |
      Oct 13, 2017

      Most likely no. The general best practice is to use a single webhook. There are some situations where more than one is needed which are outlined here.

    • Max Cascone
      Reply
      |
      Oct 13, 2017

      I assume a second webhook is needed for the Jira Bugs integration?

    • Admin
      Austin Merritt
      Reply
      |
      Oct 13, 2017

      Hi Max, in that case you would need separate JIRA integrations mapping features to the various issue types in JIRA. See number 2 in this article for more details. Once you do this, you can select which integration to use when linking with an existing issue. Thanks!

    • Max Cascone
      Reply
      |
      Oct 13, 2017

      this doesn't seem to work, at least for me. I was successful in using the bulk import feature to do this, but when trying to link an existing item with a jira bug, it doesn't work.