Follow Zube on Twitter

Create the perfect workflow with multiple workspaces

If you’ve ever wanted multiple boards for your project, this is the feature that does it! A project can now have multiple workspaces. Each workspace has its own boards, sprints, and burndown charts. Your cards now live on a project workspace and can be moved between workspaces. There’s also a new way to manage your incoming cards. It’s called Triage and it lets you quickly move your cards to the appropriate workspace.

Workspaces

All projects now have at least one workspace. You can add more workspaces to your project in the “Project Settings” view. A workspace houses your cards. Cards can only be on one workspace at a time, or they can be in Triage. Sprints are also scoped to workspaces, which means that workspaces are relatively independent of one another.

If you’d like to move cards between workspaces, all you have to do is open up a card and select a different workspace from the workspace dropdown selector. The card will show up in the default new column (probably called Inbox) of the new workspace.

Zube card showing workspace selector

Triage

When your project has more than one workspace, all incoming cards from GitHub will show up in the Triage view. The Triage view lets you order your cards; give them priorities, assignees, labels, etc.; and move your cards to the appropriate workspace when they should be worked on. You can move a card to a workspace by simply dragging the card into a workspace dropzone on the right hand side. You can also perform bulk actions in the triage view like labeling multiple cards at the same time, or moving multiple cards to a workspace at once. To perform bulk actions, select multiple cards and use the “Update Selected Cards” or “Move Selected Cards” actions.

The Triage View

If you only have one workspace for your project, you can still use the Triage view if you would like to by enabling it in the Project Settings. Also, if you’ve tried out multiple workspaces and it wasn’t a good fit for your company, you can disable the Triage view from the Project Settings page as long as you have deleted all but one workspace.

Miscellaneous Improvements

Card Numbers: Cards now have numbers, which are sequential and unique to a project. This makes it easy to know which card you are talking about in your project. The GitHub repository name and GitHub issue number are included on the card as well, so it is still clear which GitHub issue is backing the card. The search fields scattered around Zube have been updated to search for the Zube card number (or card title) and not the GitHub issue number. If you would like to search for a card by the GitHub issue number you can do so using the new GitHub issue number search field in the sidebar filter.

The other functionality change related to the new card numbers is in comment forms. You can now reference Zube cards by their Zube number by typing “z#” followed by a number. An autocompleter will pop up letting you choose a Zube card. Be sure to select the appropriate card from the autocomplete list because card references are now markdown links. Use this new feature when you want to create links that go to Zube, even when viewing the comment on GitHub. If you want to create links that go to GitHub you can still references GitHub issues the same way as before by typing ‘#’ followed by a number.

Descriptive URLs: We redid all of the URLs so they include the account, project, and workspace name if applicable. Also, since cards now have unique numbers on Zube, a card URL now ends in the Zube card number. For example “/my-company/project-awesome/c/279” links to card #279 on project “Project Awesome”. If you have hard coded URLs or bookmarks to Zube pages, those are going to break. We are really sorry about that and we promise we won’t change the URLs again so your URLs won’t break going forward.

Sprint dates: Start and end dates on sprints are now enforced. Having mandatory start and end dates is going to make reporting easier. While they are required, the start and end dates aren’t set in stone. You are free to change them whenever you like.

A design that materialized from our obsession with usability

We didn’t sit down last week to give Zube a fresh new look. All we wanted to do was to make the cards on the kanban board easier to read. But once we started, we quickly became obsessed with how good design could make it easier for you to manage your entire project. Here’s an overview of what we improved.

The kanban board

Must see more cards! We got rid of the space between the cards within their categories so they butt up against each other and form a column. Not only do more cards fit on the screen, but they are also easier to read because the new design eliminates grid illusion .

Redesigned kanban board showing filter sidebar

We also moved the board filters from the top of the board over to a sidebar on the left. What’s more, we made board filtering more powerful by adding the ability to filter on priority and creator! It’s now easier to filter out the noise and focus on high priority issues.

The issue manager

The issue manager has always been a super powerful way to manage your issues (hence the name). You can quickly filter and search across your entire project and perform bulk actions, even if your project is made up of multiple repositories. What’s been missing, until now, was a design that highlighted just how powerful the Issue Manager really is, so the new Issue Manager design is all about data density and scannability. Each issue only takes up a single line with the most important information up front. Basically, it’s an awesome table :)

The new Issue Manager design

Create a custom workflow for your kanban board and sprint board with customizable columns

It’s now possible to customize your columns on Zube. Up until now, Zube had a standard set of columns for a basic Agile workflow. In this latest release, we have added the ability to customize your columns by changing their title, adding or removing columns, and by specifying default columns for your new cards and closed cards.

The column editor

You can customize your board columns by going to the new column editor found on the project settings page. You can get to any project’s settings page from the homepage or from the left sidebar. Once you’re on the project’s settings page, you can remove any column you wish by clicking “Remove” at the bottom of each column. You can also add columns and edit their attributes.

Column editor on the Project Settings page

Column attributes and markers

Once you’re editing the columns you can change the column’s attributes, including the name, state, and status. You can also change the which column is used as the default for new cards and closed cards, and which column marks the beginning of the sprint board.

State (open or closed):

A column’s state attribute can be open or closed. Any cards that are added to the column will be opened/closed on Zube and on GitHub. So, for example, if you change the state of your “In Review” column to Closed, then whenever you drag cards into the In Review column, the cards will be closed on Zube and on Github.

Status (New, Queued, In Progress, In Review, and Done):

The status attribute indicates which stage of the workflow the columns represent. These statuses are used to track the progress of cards through the workflow. When cards are add to a column, they will be given the same status as the column. Zube Tickets will automatically track the status of their linked cards, and update their own status accordingly. We’ve also enhanced the Issues Manager so you can find cards with a particular status!

Column markers (Default New, Default Done, and Sprint Backlog)

We’ve also made it possible for you to specify which columns you’d like to have special properties. If a column has the Default New marker, then any new cards created on Zube or GitHub will appear in that column. Similarly, the Default Done marker indicates the column where closed cards will move to automatically when they are closed on GitHub. Finally, there’s the Sprint Backlog marker. The column with the Sprint Backlog marker is the first column of your Sprint Board. All columns to the left of the sprint backlog are global columns, meaning that they will always be visible on the sprint board no matter what sprint you’re looking at. The sprint backlog, and all columns to the right of it are local to the sprint, meaning they will only show cards on the actively selected sprint. And as always, cards in the sprint section of the sprint board are automatically sprinted and trackable via the burndown chart.

Happy customizing!

Manage all of your GitHub repositories together

We’re super excited to announce support for multiple repositories. You can now manage multiple GitHub repositories under a single project, and since we’ve also reworked sprints, the Issue Manager, and Tickets, the benefits are huge!

Projects with multiple GitHub repositories

It’s easy to create a new project that’s backed by multiple GitHub repos. All you have to do is select more than one GitHub repository when you create a new project. It’s as simple as that. If instead, you want to add a repository to an already existing project, that’s no problem either. Just head over to the project settings page and you’ll see a list of available GitHub repositories. You can also merge two currently existing projects together!

Project settings page showing how to add additional repositories

The Kanban Board

Once you’ve created a project with multiple repositories (sources), you’ll see a sources selector on the Kanban Board. You can select one or more repos (sources) and the Kanban Board will update accordingly. Oh, btw, we’ve also included some performance tweaks in this release so your Kanban Board will load quickly and remain very responsive no matter how many GitHub issues your project has!

Kanban Board highlighting repository source selector

Sprints and the Sprint Board

Like the Kanban Board, you’ll find a GitHub repo source selector in the filter bar at the top of the page. Since a sprint is scoped to a project, and since a project can now have multiple repos, your sprints now show the work being done across all your repos! Similarly, your burndown chart will roll up your current progress for the entire project, or you can toggle which sources your want to display on the chart.

The Issue Manger

The Issue Manager lets you filter/search/sort your GitHub issues for a project on Zube, which means, wait for it… the Issue Manager now supports multiple repositories! That makes the Issue Manager super powerful. You can filter/search/sort across all of your repositories at the same time to find exactly what you want. We’ve also enhanced the Issue Manager’s filters so you can now choose issues or PRs (or both), see open and closed cards at the same time, and of course, choose which repository you want to filter on. And since the Issue Manager is now so powerful, we wanted to give you a way to grab your data and manipulate it however you like, so we added the ability to export your results as JSON!

Tickets

Tickets are now scoped to projects… um, I feel like a broken record at this point… which means that you can link cards from different repositories to a single Ticket. Like always, the Ticket will track the linked cards and notify the Ticket owner as the status of cards change. What’s new is that the Ticket owner will remain up to date even if the Ticket involves work being done across multiple repos!

New ways to manage your GitHub Issues

This product update has many new features and improvements. We added a Kanban Board, Sprints, and multiple assignees on a single card. We also changed the layout of the Board and renamed it to the Sprint Board.

The Kanban Board

Zube’s new Kanban Board has all the bells and whistles you’d expect on a kanban board and is real-time synchronized with GitHub Issues. The layout of the Kanban Board is structured to support an Agile workflow out of the box. The Kanban Board has a standard set of categories to indicate the stage of your issues as they move through the software development process. There’s a filter/search bar at the top of the board that lets you drill down and display only the issues you’d like to see. The Kanban Board supports both GitHub issues and pull requests and you can toggle which type of cards are displayed (issues and/or PRs).

Kanban Board showing a project overview

Sprints

Zube now has clearly defined Sprints. Sprints are core to the Agile scrum methodology, and are really useful for scoping what’s important for your next product release. Sprints have been a core part of Zube from day one, but now sprints are more powerful and more flexible. While you don’t have to use sprints to get tons of value out of Zube, we suggest you give them a try! You can create and edit sprints by navigating to the Sprints page, which you can get to from the navigation sidebar under the “Sprint Board” section.

TIP: In Agile, the purpose of a sprint is to timebox your work. Sprints typically last between one week and one month depending on how your team likes to work and what you’re trying to accomplish. Milestones, on the other hand, are best used to mark the completion of a stage of your development, which means that milestones are often larger and more encompassing than sprints.

Sprints let you scope your work

The Sprint Board

After you create a sprint you can use the Sprint Board to manage your issues. Just a heads up, if you were using milestones as sprints before this release, we automatically created some sprints from you, but that won’t happen from here on out. The Sprint Board allows you to focus on one sprint at a time and makes it easy for you to bring up new sprints. At the top of the Sprint Board is the start date, the end date, a sprint selector so you can choose which sprint you want to display, and a progress bar that displays the current progress that has been made on the sprint in terms of number of open and closed issues.

The Sprint Board lets you focus on what's important

The sprint selector is located at the top of the Sprint Board, and not with the other filters, because it does not affect the Inbox or Backlog columns (the two gray columns to the left of the Sprint Board). While the filter/search bar at the top of the page will affect cards in all of the columns, the sprint selector only affects cards in the Sprint Board section. This gives you the ability to easily populate your sprints by dragging cards from the Inbox or Backlog to any column on the Sprint Board since dragging card onto the Sprint Board automatically adds the card to the currently selected sprint.

After you’ve closed a bunch of cards and the sprint had come to an end, you can head back over to the Sprints page and close the sprint. If you have any open cards on a sprint when you close it, you will be prompted about what to do with them, either move them to the Backlog column (recommended), or just remove them from the sprint but leave them in their current categories. After a particular sprint has been closed, it will no longer show up on the Sprint Board.

Miscellaneous improvements

A lot of improvements found their way into this release, I’m just going to list them out here:

  • Cards can have multiple assignees (up to ten).
  • We’ve added a shortcut for assigning and unassigning yourself on cards: ctrl + click (command + click) on a card will assign it to you and ctrl + shift + click (command + shift + click) will remove you.
  • The Sprint Board has a filter/search bar.
  • You can display PRs on the Sprint Board.
  • We added a navigation sidebar that can be toggled by clicking the “hamburger” icon located just above the sidebar in the page header.
  • There’s now the option to “Disable Automatic Card Management”. This option is found on the project settings page and will make it so Zube no longer moves your cards around for you. For example, if you have “Automatic Card Management” enabled, and you open a card in the Backlog and give it a sprint, then Zube will automatically move the card to the Ready column for you. If you don’t want things like this to happen, consider disabling “Automatic Card Management”.
  • Cards with assignees can exist in any column. So, for example, you can now have a card in the Backlog with an assignee.