These Release Notes are for ZenHub Enterprise, for customers using ZenHub with GitHub Enterprise. For all users using ZenHub on, please check out our new feature announcements on our product changelog.

What's new in ZenHub Enterprise 2.13

Below is a summary of the enhancements and new features released to ZenHub Enterprise in 2.13. Click the summary item to learn more about best practices, use cases, and tutorials for each specific feature.

Reporting enhancements

API Updates

Workflow and Board enhancements

Have questions or want a 1-on-1 walkthrough of the updates? Send us a note at and let us know how we can help. We'll setup a custom walkthrough to help you familiarize yourself with the latest updates.

Velocity Reporting

Successful development starts with a solid plan. But when time, budget, and quality are fixed, as they are in an agile software development, how can you predict the scope of work your team can accomplish in a sprint? The answer, of course, is historical data. Velocity charts are an agile tool which display a team's historical speed of work. At a glance, you're able to see exactly how much value your team can ship each sprint.

People tend to overestimate how much they can get done in a given time period, resulting in missed deadlines and frustrated teams. Using learnings from our velocity charts, we're able to make much more accurate goals.zenhub-velocity-chart

How to Read Agile Velocity Charts

If you haven't already, start adding story point Estimates to your GitHub issues and pull requests. Velocity Charts displays the total number of estimates completed in your recent milestones.

To access the charts, select Velocity tracking in ZenHub's Reports tab. The chart will automatically display both open and recently closed milestones, and you can hover over each bar to see more detail.

Note: If you have connected repositories together, your Velocity Charts will pull in data from more than one GitHub repo – giving you an even more accurate idea of your speed.

Burndown Report Enhancements

A re-designed burndown report helps teams to better track progress through a milestone. Now, burndown charts include progress bars and additional issue data on the issue list.updated-burndown

API Updates

There are two new API endpoints added that allow you to interact with Epics. These endpoints include:

  • Get Epics for a Repository — This endpoint returns an array of all the Epic issues in a repository.
  • Get Epic Data — This endpoint returns the sum of estimates for the Epic and an array with its children issues, including information on the issue number, estimate, and pipeline.

Multi-action on the Board

Multi-Action eliminates the onerous process of performing certain actions over and over again. Selecting multiple issues on the Board will trigger the Multi-Action action bar allowing you to update labels, assignees, milestones, epics, and make movements between pipelines to issues and pull requests at once.

You can select multiple issues in two ways. First, you can simply click a profile picture to select the first issue:zenhub-board-multi-action-select

Once your first issue is selected, you can continue highlighting additional issues by clicking on them. Once you've selected all relevant issues, find the bulk action you want to perform at the top of your task board:zenhub-board-multi-action-bar

You'll notice that the issues remain selected so that you can make additional updates if needed. Click either Done, Clear All at the top-left corner of your board.

Using a Multi-Repo Board?

Use bulk-actions to add new labels in repos where they don't yet exist. You can apply labels or milestones to a group of issues cross-repo and ZenHub will attempt to create those labels or milestones in repos where they didn't previously exist.

Pipeline Sorting

As a Team, different members need different Pipeline "Perspectives" (groupings) to help increase focus. Pipeline sorting helps create that focus by allowing teams to drilldown on the view that's most meaningful to their workflow.

The sort pipeline is represented by the arrow icons on the top right of the pipeline. This has moved the collapse and expand button within the cog icon. You can sort the pipeline using the following options:

  • Manual — This is the default order that will retain the prioritization (placement of issues in the list) that is set manually by your team
  • Newest
  • Oldest
  • Title A—Z or Title Z—A
  • Repo
  • Estimate
  • Assignee
  • Milestone

After sorting, the pipeline will reorder with an added sub-header to indicate what sorting is taking place. If there are issues in the pipeline that don’t contain the sorting option, they will be put in a Not Specified grouping at the end of the pipeline.

Note! Sorting by Title will not show a sub-header to indicate what is being sorted.pipeline-filtering

Board Filtering Enhancements

The Board now has a dedicated dropdown filter for Epics, including advanced filtering actions. Within the Epics menu, you're able to filter the Board to:

  • Show all Epics and substasks — this will exclude any issues on the Board that don't belong to any Epics
  • Show only Epics — This will hide all subtasks (issues nested within Epics)
  • Show all issues not in Epics — This will give you a view of all work that has not yet been assigned an Epic.
  • Filter by any open Epic — As long as the Epic isn't yet closed, you'll see this appear in the dropdown. This will filter the Board with issues and nested Epics belonging to the Epics you've selected.
  • epic-filtering

Epic cards will also show the name of the parent Epic on the Board. This means if you have a nested Epic, you're visually able to identify what Epic it belongs to without having to open the Epic itself.epic-cards

That's all for 2.13! Check out 2.14 release notes here ✌🏻!

Want to be notified when the next release notes get published? Send us a note at and we'll follow-up with the latest details once they're available.