We make extensive use of Zenhub across our development organization (1000s of developers). Enhancing the GHE integration to support the Zenhub extensions would be a huge help to our product management and development collaboration. Primary use cases are around sharing sizing/effort information during the release planning process and tracking progress through delivery.
Yes please! We have many a repo and aggregate them in Zenhub. The status defined in Zenhub would ideally be mapped to the Feature in Aha so that it is possible to View and Epic in Aha See the associated Features (from GitHub) and their Status (from Zenhub) in Aha
I'm new to Aha! but, based on my understanding of the data model, the integration/mapping should include mapping Aha! Master Features to Zenhub Epics, Aha! Feature to Zenhub Issue, Aha! Status to Zenhub Sswimlane/Column
Also this integration needs to recognize the hierarchy of Feature / Requirements when pushing to GitHub so that the ZenHub Epic is created by a Feature and its child GitHub Issues created for the Requirements and are assigned into the Epic as children
We make extensive use of Zenhub across our development organization (1000s of developers). Enhancing the GHE integration to support the Zenhub extensions would be a huge help to our product management and development collaboration. Primary use cases are around sharing sizing/effort information during the release planning process and tracking progress through delivery.
Keen for this - we have multiple Github repos in one Zenhub workspace - it would be ideal for this to be intuitively replicated in Aha.io
I'd love to discuss this with you if you're planning to do more with a ZenHub integration! We are struggling with this a bit right now.
Yes please!
We have many a repo and aggregate them in Zenhub.
The status defined in Zenhub would ideally be mapped to the Feature in Aha so that it is possible to
View and Epic in Aha
See the associated Features (from GitHub) and their Status (from Zenhub) in Aha
+1 for this feature.
I'm new to Aha! but, based on my understanding of the data model, the integration/mapping should include mapping Aha! Master Features to Zenhub Epics, Aha! Feature to Zenhub Issue, Aha! Status to Zenhub Sswimlane/Column
Agree with Chidalu: Zenhub 'Pipeline' field integration w. Aha! Status would be great.
Or a separate new field as an alternative.
Zenhub Pipeline to Aha! Status would be major key
yes!
Also this integration needs to recognize the hierarchy of Feature / Requirements when pushing to GitHub so that the ZenHub Epic is created by a Feature and its child GitHub Issues created for the Requirements and are assigned into the Epic as children
YES PLEASE :-)