Allow Custom Issue Type Integration

For complex processes, the mapping of initiatives to epics and features to stories can become problematic. The usage of Jira to drive development is hindered by the variable of interference via integration. Some cases may include:

  • The desire to prevent interference with epics, which are a special menu in the sprint/backlog area.
  • The desire to only have stories that represent correctly written agile user stories that will actually be developed, in concert with a product ownership / management process that may provide less than ideal information.
  • The desire to bring the initiatives and epics into Jira, send them through a review process, and only then create things that represent units of work. Note that the usage of status workflows is not completely helpful. While it works, sprint calculations require the closing of an issue, and more work means not closing the issue (or creating some really funky workflows, when the real solution is multiple issues that each carry part of the process).
  • Guest
  • Oct 19 2016
  • Already exists
  • Attach files
  • Guest commented
    20 Oct, 2016 07:19pm

    Thanks for the help.

  • Admin
    Chris Waters commented
    19 Oct, 2016 09:42pm

    You should see all of your JIRA issue types in the dropdown when choosing the mapping for features or requirements. Including custom issue types that you created yourself. If you are not seeing an issue type that sounds like a support issue. I recommend emailing A screenshot showing the problem would be very helpful.

  • Guest commented
    19 Oct, 2016 09:32pm

    I'm not referring to the ability to choose which issue type to sync with, but rather, the appearance of custom Jira issue types as options for this.

  • Admin
    Chris Waters commented
    19 Oct, 2016 09:12pm

    The JIRA integration already allows you to choose any issue type to sync with items in Aha!. Was there an issue type that you wanted to link which did not appear in the dropdown list?