Aha! + JIRA feature/story relationships (e.g. is blocked by, depends on) should match

If one feature depends on another, and you create that dependency in Aha!, it will not be reflected in JIRA currently. If Aha! and JIRA feature/story relationships were maintained back and forth, then we could create more realistic roadmaps and status reports.

  • Guest
  • Nov 3 2015
  • Likely to implement
  • Attach files
  • Guest commented
    November 17, 2015 14:11

    We also need this. If we go to the trouble of defining a relationship within Aha, we also need that to be reflected in Jira.

  • Sudipta Panda commented
    November 24, 2016 05:14

    This is so natural to think and add to product like Aha!. When an Integration happens from JIRA to Aha! it should automatically be done. Else there should be a Bulk Edit feature which should allow to maintain the Linked Feature in JIRA. Either way its deficient in achieving now. Kindly enable that in Aha! to make more sense. 



    SAP Ariba

  • Harrison Lynch commented
    March 30, 2017 02:48

    I wanted to try to bump this back up. It potentially solves one of the major JIRA limitations: that JIRA's hierarchy is much (too) flat relative to Aha. Basically, you can't create parent-child epics, which is severely limiting. If you could link the dependencies in Aha then have JIRA reflect these, it solves this somewhat.