Live data from Hacker News

Show HN: Zube 1.0 – Powerful project management for GitHub Issues

zube.io

51–60 of 70 posts

Re: Show HN: Zube 1.0 – Powerful project management for GitHub Issues

#51
Very nice tool, looks really polished and very functional! A while ago I also built an open-source Kanban board for Github issues using React.js and Material Design:

https://adewes.github.io/gitboard

Unlike Zube and other tools (e.g. Huboard) you can use Gitboard without giving anyone else acccess to your Github repositories, i.e. it runs completely client-side within your browser and without an intermediate server between you and Github. Currently it has much less features than Zube though.

It uses the Github API via AJAX and stores your login credentials in the session storage of the browser. Here's the Github repository:

https://github.com/adewes/gitboard

Re: Show HN: Zube 1.0 – Powerful project management for GitHub Issues

#52
Awesome work! I love how simple it is while still adding so much.

I know you've mentioned this elsewhere, but I was a bit confused by the tickets. I get what they are, but who is the intended user?

One feature I'd like to see is custom statuses. I personally am a big fan of "In progress -> Pending deploy -> Verify -> Done" instead of just "Done". It makes it really clear what just went out with every deploy, and allows the person who originally filed the issue to be the final arbiter on whether or not it was actually solved.

Another cool things would be integrations! If you have a ticketing system, it would be great if that tied into the tools that the customer support teams use. I use intercom myself, and it'd be handy if I could create a ticket out of an intercom request and remember to follow up with that user after the fix is deployed.

Re: Show HN: Zube 1.0 – Powerful project management for GitHub Issues

#53
post #44

Earlier quoted context omitted.

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?

Re: Show HN: Zube 1.0 – Powerful project management for GitHub Issues

#54

Awesome work! I love how simple it is while still adding so much. I know you've mentioned this elsewhere, but I was a bit confused by the tickets. I get what they are, but who is the intended user? One feature I'd like to see is custom statuses. I personally am a big fan of "In progress -> Pending deploy -> Verify -> Done" instead of just "Done". It makes it really clear what just went out with every deploy, and allo…

Thanks! We created tickets with non-technical people in mind as way they could report bugs, feature requests and the like without cluttering up issues for developers. Since the tickets track the work on their linked issues, the ticket owner has a clear picture of what the progress is on their ticket.

However, we've also seen dev teams hack tickets as a way to scope groups of issues together, for a feature release for example, similar to epics in Agile workflows.

Would you like to see custom statuses on board, the tickets or both?

We are really excited to add more integrations! Slack, ZenDesk and Intercom are some of the big ones we're looking at.

Re: Show HN: Zube 1.0 – Powerful project management for GitHub Issues

#55

Earlier quoted context omitted.

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!

Re: Show HN: Zube 1.0 – Powerful project management for GitHub Issues

#56
post #8

Earlier quoted context omitted.

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 o…

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?)

Re: Show HN: Zube 1.0 – Powerful project management for GitHub Issues

#57

Earlier quoted context omitted.

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 o…

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.

Re: Show HN: Zube 1.0 – Powerful project management for GitHub Issues

#59

Estimation is a killer feature missing from Github Issues, and it looks like you've got a points estimation feature, which is great. Any plans to add hour-based estimation?

It's critical to have point estimates available in Github. Zenhub, Codetree, Waffle, and others are moving to sync issue point estimation with integer labels in Github. We heavily use `1`, `2`, etc. labels in Github and have built a lot of tooling on top of their API. We'd love to use Zube, but you either need to use Github as the data source for point estimates or build a comprehensive API.
Post reply on HN