Neither ZenHub nor GitHub provide adequate visualization to help us understand hundreds of issues, Epics and their subissues, and blocker dependencies. Create a tool to create a useful visualization.
Syncing ZenHub Releases to GitHub
We use ZenHub Releases to do our project planning. These Releases are a ZenHub only implementation - GitHub has no direct linked concept, although GitHub does support the concept of Milestones. (Note that ZenHub used to integrate with GitHub Milestones, but they removed that linkage and the concept of Milestones from ZenHub.)
To provide community visibility into the issues that are in our our major releases, we should sync our ZenHub Releases to GitHub milestones.
In order to support that, write a tool which will do the synchronization for us, so we don't have to maintain the synchronization manually.
Issue Visualization
Neither ZenHub nor GitHub provide adequate visualization to help us understand hundreds of issues, Epics and their subissues, and blocker dependencies. Create a tool to create a useful visualization.
Syncing ZenHub Releases to GitHub
We use ZenHub Releases to do our project planning. These Releases are a ZenHub only implementation - GitHub has no direct linked concept, although GitHub does support the concept of Milestones. (Note that ZenHub used to integrate with GitHub Milestones, but they removed that linkage and the concept of Milestones from ZenHub.)
To provide community visibility into the issues that are in our our major releases, we should sync our ZenHub Releases to GitHub milestones.
In order to support that, write a tool which will do the synchronization for us, so we don't have to maintain the synchronization manually.