Issue Dependencies in ZenHub

Editor’s note: This blog post was originally published in May 2017 and has been completely revamped and updated for accuracy and comprehensiveness.

ZenHub Issue dependencies give teams a visualization of task relationships within a project. This allows teams with collaborative workflows to easily see what tasks they’re waiting on from others along with work they must complete to unblock other team members.

Issue dependencies mitigate risk

Sprint-over-sprint it’s important for teams to pro-actively evaluate deadlines using new information that comes during day-to-day work. Whether your team uncovers new technical issues during the implementation of another feature that impact other parts of the code, through to managing customer expectations, or even communicating a product launch to marketing and sales, project plans quickly change. When relying on just a list of GitHub issues and comment references to other Issues, there’s a strong possibility that visibility into how these changes impact other tasks get lost or forgotten.

Tracking dependent relationships between Issues and whether something is blocking another piece of work is important with any project process because it creates a central hub where everyone can communicate what’s needed without relying solely on meetings or comments to uncover important connections.

ZenHub’s Issue dependencies not only help teams visualize relationships between pieces of work, but they save team members a lot of time that would otherwise be lost just hunting down information.

Ready to get started? You can read the full documentation for Issue dependencies here.

What do you want to see next? We’re all ears! Tweet us @ZenHubHQ or send us your two cents directly.