Show HN: Zube 1.0 – Powerful project management for GitHub Issues
zube.io
zube.io
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!
Where can we find out more about Zube Tickes? Not mentioned in the simple doc page.
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?
We're working on adding multiple repos to Zube boards and should have that feature out in a couple of weeks.
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?
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?
I want to keep separate boards for my private projects, but one board for all backend related projects (backend-, aports-) in another organization.
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!
I just pushed to github with a commit message that closed the issue, (git commit -m "... closes #1", as per https://help.github.com/articles/closing-issues-via-commit-m...) and sure enough, the "card" is now marked as complete in zube, with a handy hyperlink to the corresponding commit in github. The instant email confirmation ("Ticket #n closed") from Zube could be pretty handy too, as the team grows. Nice work!
A Ticket is a place where you can link together multiple GitHub Issues that doesn't sync with GitHub itself. The Ticket tracks the status of those issues and updates it's status as the issues are worked on. This works great for bug reports that need multiple tasks completed in order to be resolved, for example.
I'm a developer that grew frustrated with so many ticket tracking solutions that force users to use the UI (Waffle and ZenHub store metadata that is not in GitHub), a lack of hackable options, and making it difficult for non-members to be involved in what's going on in a project. So, I created https://github.com/philschatz/gh-board .
Some features I haven't seen anywhere else, that gh-board does are:
- real-time collaborative editing of Issues
- showing related Issues/PR's
- shareable URL's (for remote folks)
- sequence diagrams, gantt charts, etc
- CI and merge conflict status
- "deployable" anywhere (using gh-pages or nginx)
Like other solutions, it also supports multiple repositories, Drag-N-Drop, milestone planning. In the _very near_ future it will have a burndown chart, batch editing, Issue creation, and load faster (using IndexedDB).
One of my biggest issues with Waffle or Zenhub is that loading them up is often a long wait- Zenhub can be 3-4 seconds(and often is just incorrect in labels/assignments), and Waffle could be upwards of 15 seconds.
Does this do any caching on Zube's side and then real-time update it as it goes, or am I in for a long wait again regardless?
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.
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.
Years ago I worked at a company that had a jira flow that worked with those stages for tickets and I thought it was great. Haven't been able to replicate that workflow since.
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:
On our side, Zube only accesses data related to your GitHub issues and never touches your code at all. All of the calls Zube makes to the GitHub API are whitelisted (on our end) to ensure that Zube only accesses the data it needs. For extra security, we also encrypt your auth token before storing it. It’s also important to note that your auth token is specific to Zube and at any time you can revoke your token on GItHub.
Any plans to add hour-based estimation?
Personally, I'm really excited about this, but I also imagine a lot of companies might use BitBucket for its free private repos.
The only think I kinda wish for is a way to see an overview across all repos. The GitHub issues dashboard is so awful that I wish someone could take over that job.
Multiple repo views is a great suggestion. We're working on it now and we will have it out in a few weeks!
Trying to keep project management synced between Trello and GitHub is busywork. GitHub is a major source of truth for a project, so tools that manage it are really great.
I'll be giving Zube a spin.