Link existing GitHub issues with a new Aha! Feature

The current Aha! - GitHub integration lets you sync features to GitHub issues. This won't work in the opposite way. However, It'd be nice to have an editable field to reflect that the Aha! feature is linked to a GitHub issue.

  • Guest
  • May 29 2015
  • Shipped
Release time frame
  • Attach files
  • David Hadley commented
    December 7, 2015 18:45

    It would be great to be able to not only link existing github issues to new Aha! features but also link existing github issues to EXISTING Aha! features.

  • Ethan Otterlei commented
    December 21, 2015 20:28

    We would benefit from this update!

  • Asa Ayers commented
    January 26, 2016 16:01

    As a developer I prefer to continue to use github directly, but managers are using Aha. We ran into this issue today where someone had to close several issues I created just to re-enter them into Aha. In addition to producing unwanted noise he has remember to duplicate the labels/milestones.

  • Andy Krier commented
    February 17, 2016 19:43

    We would benefit from a two-way integration for the following reasons:

    1. Developers enter bugs and reminders/todos as Github issues. As a product manager, this is great because I can easily see the volume of issues that we aren't necessarily tracking in Aha! It would be excellent to have these (or maybe only those with certain GH labels) created and synced as either ideas or Features in Aha! That way, when they make it into a release, they are already synced up to receive status updates from GH.
    2. Sometimes, Features are created in Aha! and there may already be GH Issues related to that Feature. It would be great to be able to create a Feature in Aha! and link existing GH issues to either the Feature or to Requirements on the Feature.

    Thanks for the consideration.

  • Mickaël Rémond commented
    April 8, 2016 14:43

    Will we get feedback when it gets added to the roadmap ?

  • Al Haigh commented
    June 17, 2016 20:07

    This would be an awesome update for us!

  • Jeremy Hillier commented
    July 14, 2016 14:31

    This feature would be extremely useful for us.  

     

    We don't use Aha as effectively as we could as many larger items of work start life as a github issue, and it's too burdensome creating Aha items then being forced to manually keep them in synch.

  • Steve Heffernan commented
    July 21, 2016 20:04

    We're an engineering-heavy company, and this would help us a lot.

  • Edmund John commented
    July 22, 2016 06:23

    this would be very useful

  • Blair Young commented
    February 15, 2017 19:41

    I agree with David Hadley - existing to existing needs to be included

  • Glenn Proctor commented
    April 26, 2017 13:48

    This would be very useful for us. We currently use some of the Aha-GitHub integration, but it's limited by the fact that it only works if the issue "starts" in Aha and is then pushed in to GitHub. This isn't always the case.

  • Kenny Lee commented
    June 7, 2017 20:58

    Please? PLEASE?  PUH-LLLEEEAAASE?? ;)

    For devs that live in Github, and PMs that live in Aha.io....this feature is a must.

  • Roy Zanbel commented
    October 31, 2017 18:15

    This is a blocker, there is no way to on board this feature without an option to link Aha feature with existing Github issue.

  • Victor George commented
    January 15, 2018 22:29

    I our process all the engineering communication happens on GitHub and they break features into smaller issues. We have a system mapping of one release to GitHub, and features are mapped to issues.

     

    It would be amazing if I can detect all the issues in a milestone and populate the list in Aha!, as such is the way things happen. Due to the lack of backward data import, it is really hard to keep a dual record of the same issues and manually recreate the issues, and update them, all the time. Please fix this!!!