⭐️ New

 

 

You may have noticed that the Board is looking sleeker and more modern! We made a few UI changes to help you focus on what’s important, such as:

• Pipeline expand/collapse will now be hidden until hovering over a pipeline.
• We’ve removed pipeline boarders to simplify the look of the Board.

Other changes include:

[Performance] We’ve optimized some of our core application components which should result in a 20-30ms performance improvement for all user actions in the app.

[Update] Workspace filter labels will now be applied to Epics created in the Roadmap. As a reminder, Workspace filters allow your team to only load Issues with a certain label in your Workspace.

[Update] A PR’s author will no longer appear on the list of reviewers. We apologize to any users who experienced an identity crisis after seeing their own name among the reviewers.

[Update] You’ll now see a story points summary on the Closed pipeline while searching and filtering. 

 

⭐️ New

 

 

Sprint dates

🛬 One of the biggest requests for Sprints has landed 🛬

Shuffling your teams and also need to shuffle your Sprint start and end dates? We've got you. Taking a week off to pretend like the pandemic is over and everything has gone back to normal? You keep dreaming but, even then, we've got you!

Open your Sprint configuration through the menu on the Board or sidebar…

… then click to clear and select new dates!

Assignee selector

Hopefully this has gone (visually) unnoticed but we have quietly updated the assignee selector by caching assignees rather than pulling the data from GitHub. Since being in production for the last few weeks, we've seen up to 10x performance improvements for teams with 100s to 1000s of users. We have also fixed a couple bugs along the way:

• [Bug fix] No longer freezes when searching for multiple users and then closing the dropdown without selecting anyone
• [Bug fix] No longer freezes when selecting assignees in certain conditions
  
  

And what's dessert without a few sprinkles?

• [Update] Updated the issue list in an epic to play better with the new issue flyout in the web app. Keep your eyes peeled for it landing in the extension sooooon.
• [Update] We have removed a legacy warning when editing a pipeline's name/description.
• [Update] Small UI update to the create menu to separate Sprints from the rest of the items.
• [Bug fix] Activating the "Predicted end date" in a Release report now shows the predicted end date vs previously showing an "invalid date" error.
• [Bug fix] Issues from newly added repos to your Workspaces will now include Release data on initial load vs previously needing a page refresh.
• [Bug fix] You will again see estimates of 0 on issue cards.
• [Bug fix] For our Firefox/Windows users, we have fixed a bug where browser windows that were not fully maximized took on a mind of its own and tried to start a dance party when navigating to the Roadmap. If your Roadmap experience did not include an unintentional strobe light, be thankful. To those that did experience the bug, apologies and we hope you had a disco ball nearby.

 

🐛 Fixes

 

 

Hopefully you’re not too full of Easter chocolate, because we’ve got a few treats in this week’s changelog!

You can now quickly select multiple Issues on the board by holding down the Shift key. Once selected, you can apply bulk changes to Issues, such as adding to an Epic, applying a label, or moving pipelines.

Other improvements included:

• [Update] When turning on the Automatically build new sprints feature, a suggested average velocity will now be displayed.
• [Update] Users shouldn’t see the “Unable to connect to live updates” toast as frequently.
• [Update] Issues closed on Sprint end day will now count as closed.
• [Update] The cancel button will now be disabled during new Issue creation.
• [Bug fix] We squashed a bug that made the ZenHub tab disappear from GitHub for extension users.
• [Bug fix] Some users were not seeing their Workspace filter labels pre-populate when creating a new Issue.
• [Bug fix] We fixed the bug that was causing Safari users to see the background Issues on their Board disappear when the Issue modal opens.

 

🐛 Fixes

 

 

After a series of releases for performance improvements and feature updates improving the developer experience for pull requests, we're back with a round-up of recent changes.

• [Update] Updated estimate selector in the Issue sidebar to make it easier to quickly estimate Issues

• [Update] Added more filters to Board by default (6 to 7, look for more changes coming soon!)
• [Update] Updated background colour for title + description inputs when editing an Issue
• [Update] Added error state when the Issue doesn’t exist in the Workspace
• [Update] Show search results (Issue and Story point count) during keyword search

• [Bug fix] Fixed filters rendering multiple times when searching
• [Bug fix] Fixed loading state in some filters where "No items" was showing instead of the loading state
• [Bug fix] Fixed real-time updates for the Issue sidebar when a Sprint is active
• [Bug fix] Fixed real-time updates for the Issue timeline items for Sprints
• [Bug fix] Fixed post and comment rendering in Issues for large blocks of text
• [Bug fix] Fixed bug where filters were not persisting between Board reloads
• [Bug fix] Fixed assignee lists on Issue sidebar to handle longer usernames
• [Bug fix] Fixed sprint pipeline automation when the pipeline was deleted
• [Bug fix] Fixed bug where filters were not persisting between Board reloads
• [Bug fix] Fixed arrow colour in Sprints filter when active

 

🐛 Fixes

 

 

Last year we wrote about our roadmap for improving the performance of ZenHub. Our team has been hard at work on a variety of core architectural changes that will improve the speed of the app.

Last week, in version 2.45.72, we shipped one such change that directly impacts the loading speed of the Board. You know -- the feature you probably use every single day! Through a series of optimizations and our new backend service, we were able to reduce 1 second from the average load time of the Board. A 20% improvement!

Let us know on Twitter if you've noticed any improvements on your boards. This is the first of many optimizations we are actively working on. We expect to make significant future improvements related to performance this year. If you or your team are seeing any specific performance concerns, we'd love to hear from you. Submit your feedback on our public roadmap.

 

⭐️ New

 

 

No more pesky manual linking! For all new PRs you create, GitHub keywords (fixes, closes, resolves) will now automatically link the PR and Issue in the ZenHub Board!

As Issues move through the Board, the linked PR will travel with it. When the PR is closed, the Issue will close as well - plus they’ll remain linked in the Closed pipeline for future reference.

Please note - for now, keywords can only be used during PR creation, not editing (meaning they won’t appear linked on the Board if you edit a PR to add the keyword later).

For a full list of GitHub keywords, check the docs.

 

⭐️ New

 

 

In addition to being able to link multiple PRs to one Issue, you can now link multiple Issues to one PR. Yep, we know that sounds pretty confusing. But don’t worry - the feature is very straightforward!

If several issues can be resolved with a single PR (for example, duplicate bug reports), you can connect all of those issues to the PR. As the PR moves through the board, the Issues will automatically follow - no need to update each individual ticket.

Learn more about Issue<>PR connections here!

 

📚 Resources

 

 

Since we launched ZenHub Sprints last week, we wanted to follow it up to help you get accustomed to the slight change in workflow.

If you're looking for a quick overview of Sprints in ZenHub, this is the perfect place to start.

When: March 3rd, 2021 at 10am PT/1pm ET
Where: https://www.zenhub.com/webinars/getting-started-with-zenhub-sprints

 

⭐️ New

 

 

ZenHub Sprints launched earlier this week so here's the TL;DR of what changed.

⚡️ Sprints are scoped to a Workspace whereas Milestones are tied to a repo

⚡️ Sprints are automatically created based on your set schedule

⚡️ Sprints can be automatically built from your backlog based on velocity

⚡️ Incomplete issues can be automatically rolled over to the next Sprint

⚡️ Issues can now live in more than one Sprint

⚡️ (Coming soon) The Velocity report will soon show true completion (vs always showing 100% completion when moving incomplete issues to a new Sprint)

⚡️ (Coming soon) The Burndown will soon support completion only when the issue was finished during the Sprint

Need a little more info? Check out our introduction to ZenHub Sprints or our two-and-a-half-minute tutorial.

 

📚 Resources

 

 

We are excited to announce we have raised a liiiiittle bit of money to accelerate our mission and principles of ZenHub: allowing developers to spend more time building while giving the organization access to real-time progress with no additional overhead!

If you're wondering who else has joined us on our journey, check out the details: https://blog.zenhub.com/announcing-4-7m-in-funding/