⭐️ New

Saved views have long been a favorite for customizing your Zenhub workspace, but keeping them to yourself? Not anymore. Now, effortlessly share them across your team—fulfilling one of our most requested features.

Take it further: Set any shared view as the workspace default. This unlocks tailored perspectives that persist, eliminating repetitive filter adjustments and fostering focused workflows.

• Managers: Design quarterly planning views highlighting epics and projects only, for clearer strategic oversight.
• Developers: Default to showing just your issues, keeping distractions at bay and productivity high.
• Project Leads: Create workspaces focused on just bugs and support tickets exclusively, enabling proactive issue resolution.

With shared defaults, your workspace adapts to every role and rhythm. Roll out these refinements today and watch efficiency take shape.

⭐️ New

Zenhub MCP Server & AI Integration

Introducing Zenhub MCP Server: Connect AI clients like Claude Desktop, Claude Code, Gemini CLI, Cursor, and Windsurf directly to Zenhub for a seamless development experience. Ask your AI assistant "what should I work on next?" and watch it intelligently analyze your mentions, priorities, and sprint backlog to make recommendations.

Key capabilities include:

• Create issues and set parent relationships
• Get sprint information and perform bulk updates
• Add project context for smarter AI assistance
• Prioritize work based on custom rules

API Access for All: Token generation and API access now available across all plans. Get started at developers.zenhub.com with your workspace ID and Zenhub token. MCP server setup details available at developers.zenhub.com/mcp.

Enhanced AI Chatbot: Significantly improved with broader question handling and integrated thumbs up/down feedback mechanism for continuous learning.

Goals & Planning Panel Updates

Smart Parent Selector: Automatically shows the next hierarchy level up when setting parents. Click "All Issues" if you need to jump to different levels, but the smart defaults make most workflows faster.

Performance & Shortcuts: Major performance improvements make the panel incredibly snappy, plus new keyboard shortcuts for power users - ZZ to open/close the panel, Z/ to focus the filter field.

Progress Tracking Options: Toggle between story points remaining and issue count remaining to match your team's preferred progress measurement method. Also available for sub-issue progress tracking.

Work Tracker Improvements

New sorting and timing features to help manage pipeline bottlenecks:

• Pipeline Duration Sorting: Sort by time issues have spent in each pipeline (oldest to newest or newest to oldest)
• Duration Indicators: See exactly how many days issues have been in each pipeline

• Quick Hierarchy Navigation: Jump to any parent issue level directly from within issues
• Enhanced Bulk Updates: Extended to sub-issues and issue types for faster parent assignment

Improved Issue Type Filtering: Filters now work as a group, letting you select multiple types (bug, task, subtask) and combine with other filters exactly as expected. Save any filtered view as a custom view through the Views menu.

Timeline View Updates

Sticky Issue Titles: Long issue titles now stick to screen edges while scrolling for consistent visibility across complex timelines.

Key Dates Feature: Set custom colored markers for critical deadlines. Add global key dates across your entire timeline or individual dates on specific items, giving teams clear visibility into what matters most.

Additional improvements include scroll-to-view options for multi-quarter roadmaps, progress indicators that toggle between story points and issue count, enhanced export options that now include Zenhub issues, and keyboard shortcuts for faster navigation.

Team Collaboration Updates

My Work Mentions: GitHub mentions now appear directly in My Work below your current assignments and recently completed work. Issues with mentions display in red for immediate attention, streamlining team communication.

Sprint Timezone Configuration: Long-requested feature for remote teams - set custom sprint end times and timezones for better coordination. Keep distributed teams aligned regardless of location with flexible sprint scheduling.

Daily Standup Improvements: Enhanced UI with better scroll handling, optimized performance for large teams, and Today's Insights feature for daily sprint progress visibility.

Workflow Automation & Reporting

Pull Request Pipeline Automation: Set default pipelines for new pull requests or when connecting issues to PRs. Automatically move work to Review/QA or your preferred pipeline without manual intervention.

GitHub Integration: Issue types now supported in GitHub markdown templates for seamless workflow integration.

Reporting Enhancements: Better label filtering across all reports with improved performance. Enhanced Timeline export options provide stakeholders with comprehensive sharing capabilities. Control charts feature improved table handling with priority information prominently displayed.

⭐️ New

⭐️ New

Goals & Planning Panel Improvements

Full tree drag & drop functionality

You can now drag and drop issues at any level within the Goals & Planning panel to reorganize your work hierarchy. This makes it much easier to restructure your projects and maintain the right organization as priorities change. Need to move an Epic from release 1.0 to 1.5? Drag and drop it!

Better real-time updates

Enhanced real-time updates for Goals & Planning panel issues, ensuring the data you see is always current across different views and workflows.

Improved deep hierarchy support

Planning Panel trees that are more than 6 levels deep now display properly, giving you full visibility into complex project structures.

Timeline View Enhancements

Fixed dependency line positioning

We've resolved issues with dependency lines not displaying correctly in the Timeline view, making it easier to visualize relationships between your work items.

Improved date setting via drag & drop

Fixed several bugs that were preventing you from properly setting start and end dates by dragging issues in the Timeline view.

Issue Management Updates

Better breadcrumbs

We've updated the breadcrumb navigation to make it easier to understand where you are in your issue hierarchy and navigate back to parent issues.

And more!

• If a parent issue already has 100 child issues, ZenHub will now clearly let you know that you can't add more sub-issues to it. This helps prevent performance issues with extremely large hierarchies.
• For workspaces that aren't connected to GitHub, we now properly show only ZenHub issue types in the settings, reducing confusion about available options.
• The Epics Selector no longer appears inappropriately on New Issue or PR pages in the extension, creating a cleaner experience.
• You can now quickly email support directly from the ZenHub sidebar, making it easier to get help when you need it.
• Cleaned up the interface by removing promotional UI elements that were no longer relevant.
• Added CSS fixes to improve the appearance of the AI Support chatbot window in dark mode.
• Restored the close button functionality for ZenHub flyovers to improve navigation experience.
• We've optimized when and how parent issue data is loaded, only fetching this information when you actually need it (like when opening filters or selectors).
• Resolved issues with how end dates were being set for automatically created non-templated sprints, ensuring they complete at the right time.
• Fixed an issue where the startOnTime parameter wasn't being properly passed when creating sprints from workspace templates.
• We've improved the authentication experience for both webapp and extension users, ensuring you're always redirected back to the right place after connecting to GitHub.
• Extension: Fixed scrolling issues that were occurring on GitHub's new issue pages when using the ZenHub extension.
• Extension: Resolved problems where the ZenHub extension would sometimes fail to load properly when navigating quickly between GitHub pages.

As always, reload your browser tab to pick up these changes.

These updates reflect our ongoing commitment to making ZenHub more powerful, reliable, and user-friendly. We're constantly working to improve your experience and help your team ship better software faster.

⭐️ New

Timeline Improvements

For epics which span many months across the timeline, you will now see the epic's title stick to the edge of the screen so that it can be visible at all times. We've also added an option to "Scroll into view" to quickly jump to it.

"Issue Type" Filter Behaviour

When filtering the board by "Issue Type" and using the "Matching all filters" option, the board will now consider all the selected issue types as a group. This allows you to search for things that are "('Bug' or 'Goal' or 'Story' or 'Task') and has a label 'R&D'".

Default PR Pipeline Configuration

For many years Zenhub had a hidden feature that was available only to extension users which allowed you to select the default pipeline for new Pull Requests. We've moved this feature to the "Workspace Settings" page so that any workspace member can configure it.

Parent Selector Improvements

When setting a parent issue, Zenhub will now default to showing the next level up by default. For example, if you're setting a parent for an "Project" we'll now default to showing you your "Initiatives". You can of course switch to the "All Issues" tab to see all possible options.

Sprint Timezone Configuration

For teams who work remotely across continents, it wasn't always clear when one sprint would end and another would begin. To solve this, Zenhub now allows you to view and control exactly what time sprints complete. This can be done from the "Edit Workspace > Edit Sprints" setting

And more!

• By fine-tuning how we load our JavaScript bundles, we've been able to reduce the app's initial load time by 20%.
• Added support for Issue Types in GitHub Markdown issue templates
• The number of days the issue has been in the pipeline is now shown directly on issue cards in the Work Tracker (if the "Age in pipeline" feature is enabled)
• Optimized the performance of Goals & Planning panel so that issues are displayed much faster, especially for organizations which have thousands of high level issues.
• Added support Start and End dates for high level Zenhub Issues
• Fixed a bug that prevented horizontal scrolling on the Timeline when the Goals & Planning Panel was collapsed
• Fixed a bug where the Parent filter on the Work Tracker would fail to render when no items matched your query
• Fixed a bug where extension users would sometimes see blank spaces in the GitHub issue history timeline
• Fixed a bug where Ctrl+clicking on links in the extension would not always open the links in a new tab

🔐 Security

Zenhub is now requesting access to see which GitHub organizations you belong to that we can improve issue types, GitHub Projects & collaborator workflow interoperability. Next time you login to Zenhub via GitHub you will be prompted to accept new permission scopes. The screen will look something like this:

What new permission is being requested

Zenhub is now asking asking for "Read-only access" for Organizations and teams in GitHub.

Why is this permission needed now?

It's been 11 years since we've made a change to the GitHub permissions that Zenhub needs. In those years, GitHub has evolved to add support for sub-issues, granular organization membership, and released an entirely new version of GitHub Projects. In order for Zenhub to properly support and interoperate with these new features, we need this new scope enabled.

What exactly is this permission going to be used for?

This new permission scope unlocks the ability for Zenhub to address the following long-standing customer request:

1. Allows Zenhub to better view and manage GitHub issue types. Before this change Zenhub could only see issue types configured in your GitHub organizations once those issues types have been assigned added to an issue. With the new permission scope, Zenhub can now help sync issue types across your various GitHub organizations, read issue types before they're used on any issue, and changes to issue types in Zenhub are more accurately reflected in GitHub.
2. Allow Zenhub to support import/export for GitHub Projects. GitHub has two versions of GitHub Projects (classic and new). Support for GitHub Projects classic is being phased out. With this new permission Zenhub will be able to support import and export for the newer version of GitHub Projects allowing more seamless interoperability between the two.
3. Allows Zenhub to view GitHub organizations you are a collaborator in. Sometimes users would write in to support telling us that they can't add some of their GitHub repositories to Zenhub. This was happening because they were added to those repositories as "external collaborators" without having full membership to the GitHub organization that those repositories belong to. With this new permission Zenhub can properly support this scenario and allow you to add repositories you collaborate on to your Zenhub workspace.

What if I have more questions about this change?

Feel free to reach out to us via support@zenhub.com if you have any concerns or question about this change, or want more clarification about the implications.

🚧 Maintenance

Starting today, Zenhub will begin migrating all cloud customers to our new sub-issue based Epics & Projects. If you're new to sub-issues please check out our other changelog post which describes our vision in more detail.

With this migration, you'll gain more granular work hierarchy, improved organization, and clearer alignment between your daily tasks and strategic goals—all while preserving the developer-friendly workflow your team values.

The key benefits include:

1. Additional levels of hierarchy to break down work more precisely
2. Automatic enforcement of consistent work structures across teams
3. Better visibility into how individual tasks connect to larger objectives
4. Improved Timeline view replacing the old Roadmap for better project tracking
5. Enhanced scalability as your organization grows
6. Better GitHub integration (projects and epics converted to GitHub-based issues where possible)

In this post we wanted to communicate what you should expect as part of this transition which will occur over the next few weeks. Once complete, your Projects and Epics will be converted to Sub-issue based replacements, the updated Timeline view will replace the Roadmap, and you’ll enjoy additional levels of hierarchy to break your work down more granularly.

For all customers

• All your existing roadmaps will automatically migrate to the new "Timeline" page. The Roadmap page will disappear from the main menu.
• The "Epics" filter will disappear from the Work Tracker filter toolbar. To filter your board issues by a specific epic, you can use the new "Filter by" option in the "Goals & Planning" panel
• Projects will be converted to either:
  • GitHub issues with the "Project" issue type, or
  • Zenhub issues with the "Project" issue type
• The “Epic” option will disappear from the “Create” menu. To create an epic select create a ”GitHub Issue” or a “Zenhub Issue” and choose “Epic” as the issue type
• The “Epics” metadata will disappear from the issue page (for both GitHub and Zenhub issues). This information has moved to the “Parent” metadata field instead.

For customers using Zenhub-based Epics

• You will see your Epics in the "Goals & Planning" panel in the "Work Tracker" or in the "Timeline" page. The Epics page will disappear from the main menu.
• Epics will be converted to either:
  • GitHub issues with the "Epic" issue type, or
  • Zenhub issues with the "Epic" issue type

For customers using GitHub-powered Epics

If you are leveraging GitHub-powered Epics in Zenhub (aka. legacy epics), you should expect the following changes to your Zenhub data in the coming days:

• Epics will be tagged with the "Epic" issue type in both Zenhub & GitHub
• Epics will no longer show up on the Board by default -- they will appear in the new "Goals & Planning" panel
  • If you would like to view these on the Board still, you can do this by enabling the "Epic" filter in the "Issue Types" dropdown, or updating the setting for Epics in your Issue Levels.

Known Limitations

• We have temporarily disabled the "Epic" filter and grouping options in the Velocity Report as it doesn't support the new sub-issues data structures. We plan to bring this back soon and make it even more robust (supporting different issue types other than just epics)

FAQ

How do I know if I’m using “Zenhub-based Epics” or “GitHub-powered Epics”?

If you see an “Epics” page in the main menu of Zenhub — you are using “Zenhub-based Epics”, otherwise you’re using “GitHub-powered Epics”.

How will Zenhub decide whether my Projects & Epics will become GitHub issues or Zenhub issues?

Our goal is to prioritize creating GitHub-based issues as much as possible, however, in situations where it may not be possible (ie. because Zenhub doesn't have the necessary permissions, we cannot reliably determine which repository the issue should be created in, GitHub fails to process the request, etc…) we will fall back to creating Zenhub issues.

How will Zenhub decide which GitHub repository to migrate my issues to?

We will do our best to determine this based on the configuration of your workspace and the repository of the parent issue. It’s possible we may not get this just right in 100% of the cases. If you are seeing incorrect placement feel free to reach out to us at support@zenhub.com with the details and we will correct the mistake.

If my issue is assigned to multiple Epics what will happen to it post migration?

An issue that belongs to multiple Epics will be migrated as a sub-issue only to the first Epic that contains it. In other Epics it will reference that issue as a blocking dependency.

After the migration some of my issues got duplicated with 1, 2, 3, etc… appended to the end. Why did this happen?

GitHub has a limitation of 100 maximum sub-issues. For the rare cases where your Zenhub Epics had more than 100 child issues, we created additional issue buckets to place the issues into. We recognize this is not ideal and apologize for the extra noise this creates.

After the migration some of my epics got closed. Why did this happen?

As part of this migration, we automatically closed any epics which were open but had no open children. Based on customer feedback, in 99% of cases those epics were open because a user forgot to close them. We recognize that this may not always be the right action to take. If you find that some of your epics were inadvertently closed due to this decision, please contact us at support@zenhub.com.

I received a bunch of email notifications in GitHub about new issues being created. Why did this happen?

As part of this migration, Zenhub Epics & Projects were converted into GitHub issues. We tried to respect the same issue metadata, content, and authors on those issues. Because new issues ended up being created in your GitHub repositories, if you were subscribed to email notifications in those repositories you will have been notified. We apologize for the extra noise this creates. This is a one-time migration and not something that will happen again. We hope the extra messaging we placed at the top of each migrated issues will help you clearly identify which notifications were related to the migration and which are regular GitHub notifications.

⭐️ New

Timeline view (which will replace the Roadmap)

Today, we're thrilled to announce the latest addition of our issue hierarchy project work. The Timeline view is a new take on an old favorite. Our Roadmap has served most of us really well but we all wished it did better job with more complicated work structures beyond just Projects and Epics.

We've started over and created a new timeline view that's driven by the Goals & Planning Panel which is built for hierarchy. We've taken all of your favorites from the Roadmap and then sped it up and added better drag and drop support. We've created a Timeline view that works the way you want to work. It gives you the hierarchy and structure that you need to be able to report on realtime progress of complex projects.

Very soon, we'll be migrating the old-style Zenhub Projects and Epics into new sub-issue-based replacements. Everything you see on your Roadmap will come to the new Timeline view automatically. You won't have to do a thing. The two views will co-exist for a few weeks until we're ready for that migration.

We're announcing the Timeline now because we wanted to give people with early access a way to visualize that work on a timeline. You'll be seeing it roll out soon. It might be a little earlier than we normally would release things, but it's all about bringing value to you sooner rather than later.

If you have any questions about the Timeline view, send an email to george@zenhub.com

Issue Type Colors

In GitHub, you can pick one of 8 colors for "issue types". We've added support for this in Zenhub as well. Any colors you have configured in GitHub will now be automatically synced to Zenhub and reflected accordingly across the app.

Sub-issues lister improvements

Since we started our journey towards Sub-issues you've given us great feedback along the way. Please keep that feedback coming as we read and consider everything you send! One recent request was to add the ability to see issue story points right on the sub-issues lister. This is available now!

In the near future we'll also add support for computing the full total of all sub-issue estimates so you can get a complete sense of scope for even your biggest work items.

Release Burnup Improvements

We've made several improvements to Release reports in the latest version:

• Releases with start dates in the future can now be loaded in the Release Burnup report. You won't be able to review progress towards the release (as it hasn't started yet) but you'll be able to see any issues added to the Release and its issue and story point totals.
• Fixed a bug where filtering the Release report by a label would not update the chart visualization with tracking progress for issue with that label
• Fixed a bug where selecting a Release would sometimes load the wrong Release

Other notable bug fixes

• Fixed a bug where users redeeming invites from their coworkers would be unable to join the organization
• Fixed a bug where the Zenhub extension would sometimes fail to load the Zenhub tab and metadata when navigating around GitHub pages quickly
• Fixed a bug where the Zenhub extension would sometimes display two or more Zenhub tabs when using the browser's Back/Forward buttons for navigation
• Fixed a bug where clicking on a video inside a Zenhub Issue description would launch edit mode instead of playing the video
• Fixed a bug where the open Epics would sometimes appear in the "Closed" tab of the Epics selector

⭐️ New

Quick update for you today - you can now drag and drop top-level items in the Goals & Planning Panel.

This allows you to manually sort the panel.

Note that manual sort is workspace-wide so everyone sees changes to the sort order.

Additionally, we've heard from many of you that you've been waiting for your GitHub Organization Admins to set up Issue Types in GitHub. With this in mind, we've made it so that you can set Issue Types in the Zenhub web app and once your GitHub Admins set up the Issue Types in GitHub, we'll sync the changes over. You can start working with Issue Types in Zenhub today without having to wait!

Here's a quick video to cover today's changes…

2025-02-19-product-update-drag-and-drop - Watch Video

⭐️ New

Introducing the Goals & Planning Panel

Today we're excited to release our new Goals & Planning Panel - a powerful way to visualize and manage work across your organization. This feature represents a fundamental shift in how teams can plan and track progress, bringing clarity and transparency to complex initiatives.

Why We Built This

Throughout our conversations with customers large and small, one theme consistently emerges: the need for better visibility into how day-to-day work connects to higher-level initiatives. Teams want to understand not just what they're working on, but why it matters to the broader organization.

The Goals & Planning Panel directly addresses this by providing:

• A hierarchical tree view showing the relationships between initiatives, projects, epics and issues
• Real-time progress tracking that rolls up from individual tasks to high-level objectives
• Quick filtering to see all related work on the board
• Cross-workspace visibility for true organizational transparency

Key Features

Flexible Issue Hierarchy

We've introduced 5 configurable levels of work items:

• Level 1: Initiatives
• Level 2: Projects
• Level 3: Epics
• Level 4: Issues/Stories/Tasks
• Level 5: Subtasks

Each level can be customized with your preferred terminology and default issue types. Levels 1/2/3 will automatically appear in the Goals & Planning Panel, Levels 4 and 5 will automatically appear on the board.

Intelligent Progress Tracking

The panel shows actual progress across all levels of work - not just direct child items. This means you get an accurate picture of completion, even for complex initiatives with multiple layers of subtasks.

Quick Filtering & Search

• Filter by issue type
• Search across all items
• Sort by recent updates, creation date, or title
• Company-wide view across all workspaces

Coming Soon

In the coming weeks, we'll be adding:

• Drag and Drop to manually sort top-level items
• Key dates for high-level planning items
• Visual indicators for at-risk work

Finally, the Goals & Planning Panel will be available not just on the board, but will drive our updated Timeline view (which will replace the Roadmap). You'll have the expanded hierarchy with all of the features you've come to rely on (key dates, predicted end dates, red/yellow/green risk assessments, and more!) When the Timeline view launches, we'll automatically convert your Roadmaps to the new data structures for you so you don't need to manually make any changes.

Getting Started

The Goals & Planning Panel is available now. As with all our features, we're taking an iterative approach and actively incorporating customer feedback.

Here's a video to help you get started!

goals-and-planning-panel-launch - Watch Video

Known Issues

• The Goals & Planning Panel currently requires a page refresh to display newly created Level 1/2/3 Issues. This will be resolved soon…

Feedback

I invite you to try it out and share your thoughts - email me directly at george@zenhub.com to discuss how this can work best for your team.

This is just the beginning of our vision for making work more visible and manageable across organizations of all sizes. Stay tuned for more updates as we continue enhancing this feature.

⭐️ New

Last month we released our new issue cards, the first step towards the cleaner future of Zenhub 5.

Today we've released the next few steps. We've moved some items, removed some items, and renamed some items to get closer to that cleaner future. Here's the list:

Sidebar changes

We've renamed some of our Sidebar items to better describe what they do

• We've split the Daily Feed into two pages:
  • Daily Feed (Individual View) → My work
  • Daily Feed (Team Feed) → Daily Standup
• To prepare for additional views that will be coming, we've renamed "Board" to "Work Tracker"
• We moved the Roadmap up in the list
• We've renamed some of our reports to better describe what they do
  • Sprint Report → Sprint Burndown
  • Sprint Review → Sprint Summary
  • Velocity Tracking → Team Velocity
  • Milestone Report → Milestone Burndown
  • Control Chart → Lead / Cycle Time
  • Cumulative Flow → Bottleneck Tracking

Additionally, we've consolidated all settings items under the "Edit Workspace" dropdown

Daily Feed Changes

We've separated the Daily Feed into two distinct pages.

My Work

My Work gives you a streamlined view of all of the work assigned to you. You can pick which pipeline (status) of work to show.

Daily Standup

The "Team Feed" was always meant as a "Daily Standup" view, so that's what we've renamed it.

• We've removed the tabs and streamlined what we show you
• We've removed the links and replaced them with metrics from "Today's Insights"
• You can pick which pipeline (status) of work to show

Sprint Burndown & Milestone Burndown

• We've removed the Insights & Recommendations panel as it was just too much on the screen at once - information overload! (we're taking a fresh look at how this can return)
• We've unified the layout of the reports
• We've streamlined how you filter these reports

Apologies for how cluttered some things had gotten and for how long we left them like that. We'll be back with more streamlining in the coming Sprints, but next up, the brand-new Goals & Planning Panel - stay tuned!