Better requirements link handling in Jira integration

From the Jira "READ SECOND" blog post:

 

"If a new issue is created in JIRA that belongs to a record that is already link to Aha!, then the issue will be automatically imported to Aha! This applies to issues created under a version, stories created in an epic, or sub-tasks added to an issue.

An issue will not be automatically imported to Aha! if it is created outside a linked record and then moved so that it belongs to a linked record."

It would be very useful to have move's work as well.

  • Aaron Bawcom
  • Jan 2 2015
  • Shipped
Release time frame
  • Dec 14, 2017

    Admin Response

    We have launched an enhanced Jira integration. This integration will give you the ability to import any new issues created for mapped issue types, along with several other new capabilities including the ability to:

    • Set record mappings for Aha! initiatives, releases, master features, features, and requirements and link them to nearly any corresponding record type
    • Map default or custom fields in Aha! to any “like” field and specify which direction the updates should flow (e.g. from Aha! or from Jira)
    • Automatically send outgoing changes from Aha! or choose to review and approve them
    • Import records directly from Jira to make getting started in Aha! easy
    Check out the blog post for more details.
  • Attach files
  • Luke Hanson commented
    March 9, 2017 11:57

    This integration would be extremely useful for us as we rarely create Requirements in Aha! as our developers reside in Jira, however it would be really useful to be able to produce detailed reports from Aha! as opposed to having to refer to Jira.

     

    In addition to this, the time tracking feature would be useful e.g. we estimate features in Aha! but we produce detailed estimates by breaking features into Sub-Tasks in Jira - and developers log time in Jira against these sub-tasks (as opposed to the Story).