LoginSign Up
← Back to all sparks
Z

ZenHub

PM
Velocity0.0

GitHub-native PM remodels around sub-issues and opens up to AI clients via MCP.

project-managementgithubmcp-integrationai-clientssub-issuestimeline
◆Current state
ZenHub is in the middle of a structural realignment with GitHub. The April 2025 Epics-and-Projects-to-Sub-issues migration restructured the core data model on top of GitHub's sub-issue primitive, replacing Roadmap with Timeline and unlocking deeper hierarchy. The Fall 2025 release added a Zenhub MCP Server connecting Claude Desktop, Claude Code, Gemini CLI, Cursor, and Windsurf to ZenHub, plus universal API access. Recent shipping has focused on Goals & Planning panel polish (drag-and-drop, deep hierarchy, performance) and shared Saved Views with workspace defaults.
◆Where it's heading
Two parallel arcs are visible. First, ZenHub is doubling down on its GitHub-native moat — moving the data model on top of GitHub primitives (sub-issues, projects, issue types) means its differentiation gets stronger as GitHub itself improves rather than weaker. Second, it's deliberately positioning itself in the AI-coding-tool ecosystem via MCP, betting that PM context belongs in the same surface developers already use. The May 2025 GitHub permissions update (the first scope change in 11 years) signals that even mundane plumbing is being modernized.
◆Prediction
Expect tighter integration between MCP and the Goals & Planning hierarchy (agents that can plan a sprint, not just answer questions), additional AI-client coverage as new IDE-side MCP hosts emerge, and continued GitHub feature parity as GitHub adds more native PM primitives.

◆Recent moves

  1. 6mo ago

    Shared Saved Views and Workspace Defaults

    Saved Views can now be shared across teams and any shared view can be set as the workspace default — closing a long-standing gap where personal customization had to be recreated by each member. The role-tailored examples in the release notes (manager / developer / project lead) suggest this is being positioned as a workspace-onboarding feature, not just a power-user touch.

    View source ↗
  2. 8mo ago

    Fall 2025 release — Zenhub MCP Server, universal API access, Goals & Planning polish

    ⚡ SPARK

    The Zenhub MCP Server lands, connecting AI clients (Claude Desktop, Claude Code, Gemini CLI, Cursor, Windsurf) to ZenHub for issue creation, sprint context, parent relationships, and prioritization. API access is opened up across all plans. Goals & Planning panel performance and hierarchy improvements ship alongside.

    View source ↗
  3. 10mo ago

    What's new in Zenhub in July

    Goals & Planning panel gains full-tree drag-and-drop, real-time updates, and proper rendering for hierarchies more than 6 levels deep. Timeline view fixes dependency line positioning and date-setting via drag. A 100-child cap on parent issues prevents performance pathologies. Solid platform-maturity work.

    View source ↗
  4. 11mo ago

    What's new in Zenhub in June

    Timeline gets sticky epic titles and a 'Scroll into view' option, the Issue Type filter now treats selections as an OR group when combined with other 'matching all' criteria, and sprint timezone configuration becomes adjustable per workspace. Hidden default-PR-pipeline setting is promoted to Workspace Settings.

    View source ↗
  5. 1y ago

    Request for new GitHub permissions

    ZenHub asks for read-only GitHub Organizations/Teams scope — the first GitHub permission scope change in 11 years. Unlocks better issue-type management, sub-issue support, and richer interoperability with the new GitHub Projects. Necessary plumbing for the structural realignment landing later in the year.

    View source ↗
  6. 1y ago

    Migration of Epics & Projects to Sub-issues

    ⚡ SPARK

    Cloud customers begin migrating from ZenHub-proprietary Epics and Projects to a sub-issue-based hierarchy built on GitHub's primitives. Roadmap retires; Timeline replaces it. This is a foundational data-model shift — work hierarchy is now native to GitHub instead of layered on top of it.

    View source ↗