Follow Zube on Twitter

Drag and Drop Triage

The latest release of Zube makes it easy to prioritize and triage your GitHub issues. The two most notable features are the addition of a global Backlog and an Inbox. The Backlog is board column that appears on every milestone board view. This means that you can milestone an issue by simply dragging a card from the Backlog to a milestone category (To Do, Tasks, In Progress, etc.). The ability to drag cards from the Backlog into a milestone board view is super useful when you want to populate a new milestone with a bunch of issues, and is especially useful for repositories with hundreds of backlogged issues.

Backlog and Inbox Triage Board View

Along with the global Backlog is another new column, the Inbox. The Inbox holds all of your issues that are in need of triage. You can add an issue directly to the Inbox from within Zube, or if an issue is created on GitHub, it will automatically appear at the top of the Inbox. The Inbox is an optional column that appears by default on all newly created boards and can be enabled/disabled from the board’s settings page.

Points and Color Codes

The latest release of Zube also makes it easier to estimate the complexity of an issue with Points (aka story points). Zube points are the same values as those commonly found in planning poker decks, 0, ½, 1, 2, 3, 5, 8, 13, 20, 40, and 100. Points are disabled by default but can be enabled on the board’s settings page. Also, Zube color codes (code: red, orange, yellow, green, blue), which are commonly used to indicate the priority of an issue, can now be enabled/disabled on board’s settings page.

Card with Points and Color Codes

We’d love to hear your feedback on these new features or any suggestions for future features that you’d like to see team@zube.io.

Why we created Zube

You know what’s one of the worst feelings to have when you’re working on a team?

“What the hell is everyone doing?”.

My cofounder, Jen Dewalt, and I felt this way a lot at our previous companies. Jen was hacking with the guys at Wit.ai, and I was doing web development and data science at 42Floors. We felt lost even though our teams were made up of great people who spent a good deal of time trying to keep everyone in the loop. We had weekly engineering meetings and we used GitHub issues to keep track of bugs and features. But come mid-week, we really couldn’t tell you what anyone else was working on.

We had no project management. To be fair, we didn’t really want project management. It takes work to organize and prioritize all of your issues and we tended to favor cranking out code. We tried to use various tools to help get us organized. We’d be able to keep things up to date for a while, but then we’d just stop. The cost of constantly updating the project management tool as well as maintaining GitHub issues was just too high. We weren’t willing to give up GitHub issues so we would ditch the project management tool instead.

Not having any project management tool is bad. Things aren’t so bad when you’re just a couple of developers working in a room, but once your team is a size of 5 or more, communication becomes the primary factor that determines the rate of progress… and team happiness for that matter.

That’s why we created Zube. We were working with teams of around 10 developers and desperately needed to organize our Github issues. We didn’t want to waste a bunch of time bringing up some complicated process when all we needed was some structure. Zube was born from these notions – create a virtual board with just enough structure to keep everyone on the same page and make the process so seamless that the burden of project management disappears.