It looks like a promising project management kanban tool - similar to Trello, but integrated to GitHub.
As mentioned in the comments, the current GitHub issues integration is a comprehensive integration and can work with Zenhub. With the addition of epics to Zenhub, the following workflow will work using the existing Github issues integration:
At this point, based on current priorities and community feedback, we are unlikely to make additional updates specific to Zenhub, but we would love to hear additional feedback about how this works or potential improvements that would be helpful in the comments below.
We have ProductBoard, a competitor to Aha!. We've been looking at switching away from ProductBoard because their pricing is plain stupid and they're not very customer-centric. Anyways, like Aha, ProductBoard integrates with Github issues.
We make a Feature in ProductBoard and push it to Github, where an Issue is created that's synced to the ProductBoard Feature. We can then convert the Issue to a ZenHub Epic - this doesn't affect the link between PB and GH. In ZH, when all of the children Stories are closed, the parent Epic is closed which is reflected in PB. So the basic integration "just works"
But as the last commenter observed, there are a LOT of other integration points that are missing. Like syncing of Story Estimate/Effort, Release Planning and Roadmap Planning.
If there was a ZH + Aha! integration, we'd switch in a heartbeat.
Keen for a more robust integration - we have multiple Github repos in one Zenhub workspace - it would be ideal for this to be intuitively replicated in Aha.io
Please take a look at Zenhub Epics and Aha Epics. Now that Zenhub has api access, could be an easy integration with a nice ROI (as well as more rich status updates back from zenhub)
If you had the Zenhub Epic integration, it would be a no brainer for us to adopt Aha!
Can the second step of the above workflow be eliminated? Why would an Aha! Epic ever *not* be a ZenHub Epic? Asking the user to make this second click is quite annoying (especially when you're onboarding to Aha and already *have* a pile of epics that you have to move issues out of and into Aha! epics).
As per Andrew's comment I think ZenHub's addition of Epics does mean more work would add significant value.
I agree with Andrew's comment about Zenhub epics. Perhaps a good starting point would be the ability to send an initiative to Github. We could then use Zenhub once it has moved across to convert the issue to an epic.
Zenhub has just added epics, which makes organisation quite good and of course should be tightly integrated into initiatives
It looks like Aha!'s current GitHub Issues integration can work with ZenHub since ZenHub organizes Issues into a Kanban board flow - but I suspect there are additional integration points Aha! could take advantage of.