[mbym]

Oh, this is really cool. So when I create a "card" on zube, it automatically creates an issue on github. And when I drag the card to "done" on your trello-like board, it marks the issue as closed in github. The zube interface definitely adds a lot of clarity with colours and birds-eye view. I'm excited to use this! I think the onboarding could make it easier to quickly understand this much (initially, I falsely assumed a "ticket" corresponded to one github issue).

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!

[jenniferDewalt]

Thanks for signing up! We definitely have some work to do with the on boarding flow and documentation, especially around Tickets. Glad to hear you were able to figure it out! :)

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.