jenniferDewalt

Thanks for the kind words! Glad to hear Zube is working for you! :D

That's a great idea and would be pretty quick to add. Would having either points or hours for a repository work for you?

We are definitely interested in adding GitLab support as well as other integrations though I'm not sure when we'll get there.

Thanks Jason! That is exactly where the idea for Zube came from! Trying to keep two (or more!) data sources in sync is error prone and just generates extra work for everyone. We made Zube to combat that problem.

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?

Great question. We built Zube is speed in mind even for repos with hundreds of open issues. If you have over 1000 open issues you'll probably notice a lag on any platform and it will take about 2 seconds on Zube. We're obsessed with speed and we'd be happy to work with you to make things fast!

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

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.

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...

Thanks for the kind words! We started with GitHub because that's what we know and love but down the road we'd love to add more integrations like BitBucket.

Multiple repo views is a great suggestion. We're working on it now and we will have it out in a few weeks!

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.

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!

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!

Got it! I can see that being helpful when looking at other site metrics.

This looks very useful! I'm wondering if it's possible to see a timeline of changes, like the history of changes for the last 30 days?

We can run queries against events like issue open/close, labeled, miletstoned etc. so we can generate reports with time analytics. If it is just card open to close time, we could definitely bump that up or list!

Thanks, that sounds like good advice.

What type of environment are you working in? Those are great suggestions for integrations and we are very interested in adding integrations that help developers. Is there one that would make Zube usable for you?

Thanks for trying it out! At the moment you can only view issues by milestone. We're working on a 'power user' view where you'll be able to view all of your issues, perform batched actions and other global type actions.

Huboard's cool and it's open source! Zube gives each developer their own row, so it's different from a traditional kanban board.

Not related beyond us both wanting to make GitHub issues better :)

Thanks for trying it out! To edit a card, click the card on the board to open the card. Then you can click the title to edit it. Milestones and labels can be changed from the sidebar by clicking the gear or heading. At the moment you can't edit the initial comment with the card but we should have that fixed soon.

I'm not sure what you mean by your second question. On Zube, the In Review doesn't have a concrete meaning, that is, it doesn't affect the card's state beyond who the issue is assigned to. At Zube, we use the Review column for cards that we have completed but still need to test, have code reviewed or just want to keep an eye for unknown bugs.

ZenHub is a great plugin for GitHub. It adds a kanban style board to your GitHub issues. Zube is not a Chrome extension, it's a full web app. The reason we made it a web app is because we really wanted to focus on making a product that developers love. With Zube you don't have to go to GitHub issues, and we believe the experience on Zube is much better than GitHub Issues.

Also Zube is fast :)

You can see our focus on developers by the layout of our board, which is more scrum style than kanban. Each developer has their own row. It makes it easy to see exactly what your tasks are. You can also assign issues by dragging the card over to the user's row, something that isn't possible with a kanban board like ZenHub. We care less about getting an overview of the whole project (what PMs care about) and more about what needs to be done (what devs care about)

We'll continue adding features that make developers happy whether they would fit into the GitHub Issues paradigm or not.

Sorry, sp332. I only sent this email out to people who I thought would be interested in a new project of mine because they were interested in my other projects (180 Websites in 180 Days and YumHacker).

I don't mean to spam anyone and I'll remove you from my list.

Edit: To be clear, I only sent emails to people who have given me their emails previously. I didn't scrape them from the internet.

Sorry again!

Would love to hear about any other features you think your team might find useful.

Thanks! We're super focused on making developers happy. We're going to continue to make features that help developers be more productive and organized. One feature we've been thinking about is personal todo lists that live outside of your Zube boards.

I generally receive constructive feedback via email and I am always happy to receive more. The source for YumHacker is on GitHub.

The response from the community has been amazingly and wonderfully supportive. My comments in the post were mostly a reflection on the weird things people have said to me personally. For example, I had a close family member look me dead in the eye and say, "You shouldn't have started this project."

Before I started the 180 project I made a list of every idea I could think of. Then as the project went along I was often inspired by something I came across the day before or a new concept I wanted to explore. I had a few moments where I thought I'd never have a good idea again.

I quit my job last year and have been working on the 180 websites project and now YumHacker full time. I spent on average 10 hours a day on the 180 project.

I pulled lots of bits and pieces from all over the place but some of the big helpers have been Stack Overflow, MDN, HTML5 Canvas Tutorials, Rails Tutorial, GitHub, jQuery docs, and the Rails docs. I read tons of blogs and demos as well.