Skip to Main Content
Status Unlikely to implement
Categories GitHub
Created by Donna Sawyer
Created on Jun 28, 2017
Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit A-I-11496 Support for Zenhub in the Github Enterprise integration.

Integrate with Zenhub columns (Kanban board for status) Merged

Teams using Github with Zenhub in product development would like Aha! status to map to the name of the Zenhub column in the Kanban board.

  • Andrew Foster
    Reply
    |
    Sep 1, 2021

    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.

  • Duncan from controlla.io
    Reply
    |
    Feb 11, 2020

    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

  • Doug Chase
    Reply
    |
    Nov 8, 2019

    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.

  • Lisa Stidham
    Reply
    |
    Oct 9, 2019

    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

  • Kam Yee
    Reply
    |
    Jun 20, 2019

    +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

  • Robert Oberhofer
    Reply
    |
    Sep 17, 2018

    Agree with Chidalu: Zenhub 'Pipeline' field integration w. Aha! Status would be great. 

    Or a separate new field as an alternative. 

  • Chidalu Onyenso
    Reply
    |
    Sep 5, 2018

    Zenhub Pipeline to Aha! Status would be major key

  • Guest
    Reply
    |
    Aug 28, 2018

    yes! 

  • Guest
    Reply
    |
    Aug 28, 2018

    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

  • Patrick LaRoche
    Reply
    |
    May 3, 2018

    YES PLEASE :-)