Follow Zube on Twitter

Beautiful and powerful charts

Our new charts provide insights into your project like never before. There are several new charts that let you dig deep into what’s being accomplished. The truly wonderful thing about the new charts is that they give you an overview of all your data in one place, no matter where the work is being done. If you have GitHub sources linked to your project, then your GitHub data is right there too.

Burndown, Burnup, and Velocity

If you’re using sprints, and we suggest that you do, you’ll be delighted to see that we’ve added card counts to the Burndown chart. Zube will automatically track card counts for all of your sprints going forward. As a note of caution, we just started collecting card count data so don’t worry if card counts for old sprints are flat lines.

A Burnup chart with a changing goal

We’ve added a Burnup chart, which is similar to a Burndown chart except that there’s a goal line at the top instead of working toward zero. The great thing about the Burnup chart is that it allows you to see changes to your goal. In an ideal world, your goal would never change during a sprint, but in the real world it often does. With the Burnup chart you’ll be able to see exactly when cards or points were added to your sprint and by how much your goal changed as a result.

An important notion in Agile, and particularly Scrum, is the idea that your team’s efficiency should be improving over time. The first step towards increasing your team’s efficiency is to measure how much work your team is doing per week. A good way to display this information is with a velocity chart. Zube’s new Velocity chart shows the total cards or points closed per sprint so you can get a clear picture of how much work is getting done in that fixed time period. Your sprints are displayed side by side so you can make sure your team is improving over time (or at least holding steady).

Throughput and Users Throughput

Sometimes you just want to see a raw measure of what’s getting done. The Throughput chart shows you how many cards or points are closed each day. There’s a powerful set of filters that let you drill down to see just what you’re interested in.

A Users Throughput chart where each team member is a slice of the stack

The final chart we added is the Users Throughput chart. The Users Throughput chart lets you see how many cards or points each team member is closing per week. It is a stacked area chart, segmented by user, so it’s easy to see how everyone is doing over time. The Users Throughput chart makes it easy to see who is getting bogged down or which team member has really stepped up their game.

Work side by side with the development team

Zube loves developers and up to this point you needed to be a developer with a GitHub account to get the most out of Zube. That’s all changed! We couldn’t be more pleased to announce that Zube now lets you log in with Google so everyone can work seamlessly with the development team! This major enhancement is made possible by Google Login and the new zubebot.

The homepage with Google Login

Google login

You can now use Google login to access Zube, which is perfect for nontechnical team members who do not have GitHub accounts or really shouldn’t have access to your codebase. When you log in with Google, everything on Zube works just as you would expect. The only drawback is that you cannot change Zube cards that are backed by GitHub issues. If you don’t want your nontechnical team members to be able to change GitHub backed cards, then you’re all set. If, on the other hand, you do want Google users to be able to interact with all the cards on Zube, you can enable the zubebot!

The zubebot enables a frictionless workflow for everyone

Installing the zubebot means that everyone using Zube can change whatever they want! The zubebot handles the syncing with GitHub so everything will stay up to date in real time. The power of the zubebot is that it unlocks all the cards so you no longer need to give team members access to your GitHub repos just so they can manage cards on Zube. If you would like all your team members to be able to use Zube to its fullest, you’ll want to install the zubebot. We highly recommend installing the zubebot.

Tips and tricks

A couple of things you might find useful:

  1. If you log in with Google or GitHub and you are already a Zube user, we will automatically try to merge your accounts for you. You can also link your Google and GitHub accounts together by going to your user “Profile Settings”.
  2. Adding Google users to your account is slightly more complicated than adding GitHub users. First, have your team members sign up for Zube using Google. Then, you can add them to your account by searching for their usernames on the “organization settings” page. Once you’ve added the Google users to your organization, you can add them to the projects you’d like to give them access to.
  3. You can add the zubebot to your account by going to your Zube “organization settings” and clicking on the “Integrations” tab. There’s an install button that will take you to a GitHub page where you can install the zubebot. Note that you must be a GitHub organization “Owner” in order to install the zubebot.

You can find more details in the docs.

Create cards that don’t go to GitHub

For most companies, not every card on Zube also needs to be a GitHub issue. Zube now lets you to create cards without creating an associated GitHub Issue. If you later decide that your local Zube card needs to be on GitHub, that’s no problem either. You can easily add the card to a source repository by selecting one on the card’s sidebar.

Zube card showing source selector

Seamlessly manage GitHub issues and local cards together

On Zube, your local cards function in the way you’re already used to. To create a non-GitHub backed card, select ‘Only on Zube’ from the source selector when you’re creating a new card. That’s pretty much all there is to it. Your local cards will appear right next to the GitHub backed ones on the kanban board, the sprint board, and the Issue Manager. You can also add local cards to epics, tickets, and sprints, just like their GitHub backed counterparts.

How to use local cards

There are many use cases for local cards, but I’ll highlight a few.

  1. Use local cards to plan new features. Imagine you are the product owner. You know that an important part of Agile project management is to continually refine your requirements by talking to your customers. When you do this, you’ll likely get a bunch of good ideas about how the product can be improved. Your ideas are probably more nebular than specific engineering tasks, so instead of making cards that get sent to the engineers on GitHub, make local cards! You could do this right on your main board if that makes sense for your team’s workflow, but I’d suggest creating a separate workspace for product features that are still in the idea phase. Then at a future date, when you have a clear picture of what needs to get done, you can create the necessary engineering tasks, or convert your local cards to a GitHub Issues by adding a GitHub source.
  2. Use local cards for your non-engineering teams. Your company probably has a workflow that involves multiple teams. Maybe the design team and the product team spec out what they’d like to see before handing it off to the engineering team. And when those new features are ready, they need to be marketed. Local cards let your non-engineering teams use the same system as your developers without adding clutter to the developers’ GitHub repositories.
  3. Use local cards to keep private data off of GitHub. Sometimes you just don’t want certain tasks to go to GitHub. There are a bunch of reasons for this but if you’re using Zube to manage a repository on GitHub where the entire world can view the GitHub Issues there, you might not want a critical vulnerability to be public knowledge. At least until you’ve fixed it.

Never miss an important update on your project

An important part of Agile project management is being able to quickly adapt to changing requirements. This latest release introduces notifications, which allow you stay up-to-date with what’s happening across your projects. You can now specify general notification settings for your project, as well as subscribe to individual Cards, Epics and Tickets.

Notifications inside of Zube will appear in the header under the bell icon. The notification icon will turn blue with a red dot when you have unread notifications.

To change your notification settings, head to your Project’s Settings page and click the notifications tab where you’ll see the notifications options for Cards, Epics and Tickets. You can chose what level of notifications you’d like to receive for each item both via email and inside of Zube. There are three notification levels:

  • Following: Following means that you will receive notifications for all important events for Cards, Epics or Tickets such like when a Ticket is created or the status of a Card changes.

  • Not Following: Not Following means that you will only be notified when you are subscribed to; @mentioned within; or assigned to a Card, Epic, or Ticket. This is the default setting.

  • Muted: Muted means you will not receive any notifications unless you are subscribed to individual Cards, Epics or Tickets.

You can change which email address you’d like your email notifications sent to from the settings page as well.

Customize your notification preferences

We’ve also released a Slack integration! You can now be notified of important events on Zube via Slack. To integrate Zube with Slack, head to the Project Settings > Integrations page, click the Add To Slack button and follow the authentication directions.

Seamlessly organize and track your cards

If you have a bunch of cards that belong together, you can now group them together using an epic. Epics are a fundamental component of Agile and are made up of a bunch of Agile stories, hence the name. But you don’t have to subscribe to a particular flavor of Agile to get a ton of value out of epics on Zube. Once you have grouped some cards together into an epic, you’ll be able to see how the cards are progressing through your workflow, and the status of the epic will automatically reflect the status of its linked cards.

Viewing all of your epics

You can see all of your epics on a project by clicking on the Epics link on the navigation sidebar. You can then quickly filter and sort your epics to find just what you’re looking for. The epics listed out on this page have a progress bar overview of their cards that displays both card count and the number of story points. You can also create new epics on this view using the “New Epic” button at the top of the page.

Quickly find and sort your epics

A single epic

When you open an epic, you’ll see a list of its cards, broken down by card status, as well as a progress bar overview. On the right is a chat area so you can talk about your epic. You can quickly add cards to an epic from this view by either creating a new card or searching for an existing card. If you happen to be somewhere else in the app, you can add a card to an epic by opening up the card and selecting the appropriate epic from the Epic dropdown on the card sidebar.

An epic with attached cards

How to use Epics

Since epics are a new addition to Zube, here’s how we think they might be incorporated into your workflow. Epics are used to describe higher level concepts than cards, so it is probably easier to start by first making an epic that describes what you’re trying to accomplish. Then, from the epic show page, create all the cards (stories) that describe the work that needs to be done to complete the epic. You could now give your cards priorities, points, and assignees directly from the epic show page, but you’re probably better off switching to the Sprint Board (or Kanban Board or Triage) and organizing your cards there. If you’re doing scrum, or any sort of sprint based releases (which we recommend) then you’d proceed as usual by creating a new sprint and putting whatever cards on the sprint that you think you can accomplish during that period of time. It is typical for a single epic to span multiple sprints, so you shouldn’t be overly concerned about trying to get all of the cards from an epic onto a single sprint. Most of the time you’ll be better off working on the cards that fit naturally into the sprint, which are the blockers and other high priority cards. That said, the sooner an epic is finished the sooner you get to deploy that awesome new feature, so don’t let open cards dangle on an epic for too long before you complete them. And if you’re trying to figure out how epics and sprints differ, epics are used to group together cards that collectively achieve some goal, and sprints are used to timebox your work so you can measure and improve how well you’re cranking out new features. We hope using epics will keep you more organized so you can ship code faster than ever.