Hacker News Reader

Comment by jenniferDewalt | Hacker News Reader

Hi! I’m Jen, cofounder of Zube and we’re thrilled to announce Zube 1.0 today. Zube 1.0 is much more powerful than our beta version. We’ve added Zube Tickets, which lets you create tickets that track groups of related GitHub issues. Think ZenDesk for Github. We’ve also added an issue manager, which is the fastest way to find and triage your issues on any platform. And there have been many improvements to our scrum/kanban board like a new pull request section and burndown charts.

We’d love to hear what you think of Zube 1.0 and I’m happy to answer any questions you have in the comments here!

View on HN

Hey Jen,

Congrats on 1.0. Our development team uses a micro service architecture that has 1 project spread across multiple repos, and I think the biggest problem with most project management software with extensive Github integration is that they are on a per repo basis. We can never get a holistic view of our entire application without duplicating work into another Project Management platform. Is there anything inside Zube that would alleviate this? How does Zube handle multiple repos for teams?

We're working on implementing multiple repos on one board right now and will have that feature out in a couple of weeks.

Are you looking for adding several repos to one board or do you need a board that displays issues from one or more repos as well as non-issue backed tasks?

Just one board with all the issues from multiple repos would be great! I think keeping non-issue backed tasks seperate makes sense.

Sounds good! Yes, I agree that the board should really only be for issues.

Just one board for all projects _per organization_, please.

I want to keep separate boards for my private projects, but one board for all backend related projects (backend-, aports-) in another organization.

Cool! That's how we're implementing it.

Will it be possible to group a number of repos inside one org as well? E.g. repos A and B form one group and repo C is separate?

Yep, that's the game plan!

Not exactly what you're looking for, but Netflix OSS Tracker aggregates metrics across GH project.

https://github.com/Netflix/osstracker

Is Zube a direct result of your 180 days of coding exercise (https://news.ycombinator.com/item?id=6097155) that you did a while back? If so, amazing. Very inspiring

Thanks! The idea for Zube came from my and my cofounder's (shout out to @204NoContent!) experiences working on dev teams at our previous jobs at early stage startups. We built the tool we wished we had :)

The 180 Websites project is definitely a part of what led me to be a technical cofounder. It certainly helped me learn how to ship code and iterate!

Hi Jen - is Zube 1.0 for people in the company who are not developers?

Yes! We made Zube Tickets so support teams and non-technical people have a place to report problems/questions. The cool thing about Zube Tickets is that they automatically track what the development team is working on and notify you when things get done. This makes it easy to know what's going on without having to understand the technical details of every GitHub issue!

Sound intriguing!

Where can we find out more about Zube Tickes? Not mentioned in the simple doc page.

Yea, our docs are a little short when it comes to Tickets. :) We'll work on getting that updated but in the meantime you can check out this blog post - https://zube.io/blog/introducing-a-ticketing-system-for-your...

Can I add non-technical people to Zube, without giving them access to repos on Github?

At the moment, you need at least read access to the repo to use Zube but we're working on allowing email only login for non-technical people to use tickets and view the Zube board. We're aiming to have that out in a few weeks.

How does it compare to Waffle.io?

Zube and Waffle are similar in the sense that we both allow developers to better organize their GitHub issues on a kanban board. The main difference between Waffle and Zube is that Zube provides many features that Waffle lacks. Zube lets team leads easily triage incoming issues with a powerful issue manager. Zube allows GitHub issues to be grouped together into a single ticket, and automatically tracks the progress of the underlying issues. Zube has story points and burndown charts. And Zube’s GitHub integration allows you to fully manage your issues, labels, and milestones, whereas Waffle’s less complete integration does not. So I guess you could say that Waffle is a simple way to visualize your GitHub issues and Zube is a project management platform for your GitHub issues.

Thank you for the extensive explanation! We'll give it a try ;)

Awesome! We'd love to know what you think!

>> Zube’s GitHub integration allows you to fully manage your issues, labels, and milestones, whereas Waffle’s less complete integration does not.

Meaning labels and milestones can be created from Zube instead of being limited to just applying already existing labels and milestones like Waffle? Can multiple repos be combined into a single board like Waffle?

Yep, you can create, edit and delete labels and milestones from Zube.

We're working on adding multiple repos to Zube boards and should have that feature out in a couple of weeks.

Why would one pick Zube of Jira? (I am about to implement Jira - are you mature enough to compete against Jira, thus shall I eval Zube V Jira? or diff use case?)

Great question! JIRA is highly configurable so if your company has a lot of custom requirements, that might be the way to go. Zube provides a lightweight, Agile workflow out of the box designed to get you up and running fast. So it depends on your companies' needs, but if you have a development team that loves working in GitHub, Zube has better GitHub integration than JIRA.

Congrats Jen! I remember when you showed me this in it's early stages at Heavybit. It's really come a long ways with features and polish!

Thanks for the kind words Stephen! We've come a long way since that rickety demo :)

Reply on news.ycombinator.com