Follow Zube on Twitter

Cards on the Kanban Board and the Sprint Board now show related GitHub Pull Request information right on the front of the card. Previously, it was possible to see all the related Pull Requests (and other cards) on the card show view, and that hasn’t changed. What’s new is that Pull Request information is now available on the front of the card, so you can get a handle on related Pull Requests and their statuses at a glance.

Kanban Board showing Cards with Related Pull Requests

Using Pull Requests

There are two common ways teams use Pull Requests. One approach is to use Pull Requests to scope code that’s supposed to be deployed together, perhaps as a release. These Pull Requests tend to be quite large and include lots of code changes. The benefit of using Pull Requests in this fashion is that once the Pull Request is merged, you know that your code is ready to ship. Another benefit is that there tends to be only a few Pull Requests open at a time, and there may only be one active Pull Request. This makes it easy to focus on getting your code ready to ship without extra management overhead. The downside is that your Pull Requests drag out for a very long time and become quite bloated with code that might not sum up to solve any business objective.

Another approach to using Pull Requests is to have them define a feature that you’re building. This approach is more popular with teams that have implemented continuous deployment. The benefit of having your Pull Requests define a feature is that the code that’s wrapped up into them works together to solve a business objective. Merging the Pull Request means that you’ve successfully implemented at least one unit of value for the company. This aligns itself more naturally with the philosophy of Agile project management, where a collection of user stories (Cards) sum up to describe a feature (Pull Request). The downside of using Pull Requests to define features is that there tends to be a lot of them around at the same time and you need to make sure none of them are slipping through the cracks.

We hope the new Pull Request information on the front of cards will make it easier for you to quickly determine which cards are part of your pull requests and let you ship with confidence, no matter what approach your team uses.

Custom tailor your notifications across every channel

You’ll love the new level of control you have over your notifications. You can now configure project and workspace notifications separately, so you can receive just the events you’re most interested in. We’ve also extended our Slack notifications with new events and restyled our own notifications.

Beautifully clear and concise

At Zube, we’re all about data clarity, and the style of our new notifications reflects that. Each notification is designed to be recognizable at a glance and fully digestible as quickly as possible. The new style unifies the way email and in-app notifications are presented so you can enjoy the same level of clarity in both places.

New Email Notification

Workspace Notifications

The great thing about being able to control your workspace notifications is that you can zero in on the boards that are most import to you. You can follow, not follow, or mute individual workspaces so you’re only subscribed to the most relevant cards. You can also go one level deeper and customize which specific events you’re interested in.

Project Notifications

We’ve also beefed up project level notifications for Tickets, Epics, and Triage Cards. Just like workspace notifications, you can configure your subscription level as well as select which individual event notifications you’d like to receive.

Slack Notifications

We’ve also enhanced the Slack notifications even more. You can specify exactly which status changes you’d like your channel to receive for Tickets, Epics, and Cards. In addition, you now have finer control over Triage and Workspace notifications.

Happy Configuring

The new notification system is very powerful because it gives you full control over which notifications you’d like to receive and where you’d like to get them. We highly recommend that you take a few minutes to configure your notifications just how you like them. There are quite a few places where you can do this, so be sure to check your Notification Settings and Triage Notification Settings at the project level, and then visit every workspace to adjust your workspace notification settings there. We really do hope that the clarity of our new notification system will bring a smile to your face.

The notifications you want, right where you want them

Keep your team in the loop with what’s happening on your Projects and Workspaces with Zube’s new and improved Slack integrations! You can now customize your Slack notifications based on Project or Workspace so every team gets the information they need without any extra noise.

Installing a Slack integration

To install a custom Slack integration, navigate to the Project Settings page and click the Integrations tab. Then, click the Create a New Slack Integration button to open the Slack Channel Integration builder. In the integration builder, chose the Project or Workspace scope and then select which notifications you’d like to receive in Slack.

Slack Channel Integration Builder

After you’ve configured your integration, click the Add to Slack button and follow the directions to select the Slack workspace and channel for your integration. Once you’ve authorized the integration, Zube will begin sending your custom notifications to Slack.

You can create unlimited Slack channel integrations to send custom notifications to everyone on your team.

A few awesome enhancements

We added a few things to Zube recently that are designed to make your life easier. First up is the ability to order your cards in any kanban column. You can now order your cards at any time using the dropdown in the top right of any kanban column. You can order by Priority, Points, Newest, or Oldest. Ordering by priority is particularly useful because it is a great way to keep your backlog prioritized.

The ordering function of a kanban column

Another similar enhancement is the ability to Archive all cards that are in your Done column. There’s a small button in the upper right of the column that does just that. It’s a great way to clear out a crowded Done column if you have a traditional kanban workflow. For teams that use Sprints, it is worth pointing out that Zube automatically Archives all of your closed cards once a sprint is closed, so there’s no need to do it manually.

The third enhancement is expanded file support for uploads. You can now upload a bunch of file types like .csv, .pdf, and Microsoft documents like .docx, .pptx, and .xlsx.

A comment form with expanded file support

We hope these enhancements bring a little more joy to your day, and as always, please feel free to reach out to us to let us know what you’d love to see next.

Keep Your Zube Cards in Sync with GitHub Column Labels

The new Column Labels feature lets developers on GitHub easily see and manipulate a card’s category in Zube. When you turn on the Column Labels setting for your Workspace, Zube will create special labels on each of your project’s GitHub source repositories for every column. When you move a GitHub backed Card from one column to another on Zube, the GitHub Issue will be updated with the corresponding column label.

There’s more good news! The Column Labels feature works the other way around as well! If a Zube column label is added to an Issue on GitHub, Zube will automatically move the Card to the appropriate column.

A GitHub Issue showing a Zube Column Label

You can enable Column Labels for GitHub backed Cards on the Workspace Settings page. Also, it is highly recommend that you install the Zubebot when using Column Labels for a seamless experience.

We hope the new Column Labels feature makes it even easier for your entire team to plan, track, and manage your projects whether they are on Zube or on Github.