Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

zube.io

Post reply on HN
Print view View original

61–70 of 70 posts

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

#61

Post by jenniferDewalt »

kwiens wrote: post #59
alexwebb2 wrote: post #28

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.

Interesting. Maybe we could make an app setting that would save points as labels. Thanks for suggesting it! And we will release a public API :) You can already see much of the functionality in Zube's Issue Manager.

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

#62

Post by lemming »

philschatz wrote: post #32

Oh nice! I like the ability to assign Issues by just dragging to a user and the "Batch Editing" UI is pretty concise! Also, being able to create an Issue without having a GitHub login seems helpful to get non-developers communicating. 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 o…

This looks really nice - thanks!

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

#64

Post by jenniferDewalt »

nzoschke wrote: post #63

This is great. 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.

Awesome! Let me know if you have any questions. I'm happy to help!

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

#65

Post by jmtulloss »

jenniferDewalt wrote: post #54
jmtulloss wrote: post #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 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…

Oh I was thinking of the board, not tickets. But perhaps it's more relevant in tickets? I'm not sure, just an idea.

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.

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

#66

Post by jenniferDewalt »

jmtulloss wrote: post #65
jenniferDewalt wrote: post #54

Earlier quoted context omitted.

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…

Oh I was thinking of the board, not tickets. But perhaps it's more relevant in tickets? I'm not sure, just an idea. 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.

Gotchya! We've been thinking about how to add some flexibility to the columns without falling into the 'endless column' trap where teams end up with dozens of micromanaged columns. It sounds like that level of organization would still fit the paradigm.

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

#67

Post by x0ner »

This looks really cool and is something I would love to check out, but the permissions of the actual app seem pretty high. For us, our code is stored in a private repository with no plan for any public release. Permissions for Zube are asking to not only read the private repository code, but also have write access to them as well. There's also requests to read/write web service hooks, deploy keys and pull requests. Is this a byproduct of Github's design or does the app really need all of these permissions to function properly?

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

#68

Post by jenniferDewalt »

x0ner wrote: post #67

This looks really cool and is something I would love to check out, but the permissions of the actual app seem pretty high. For us, our code is stored in a private repository with no plan for any public release. Permissions for Zube are asking to not only read the private repository code, but also have write access to them as well. There's also requests to read/write web service hooks, deploy keys and pull requests. I…

We totally understand your concerns and we take security very seriously. In order to manage GitHub issues, GitHub currently requires the repo scope. If there was a more restrictive scope just for GitHub Issues, Zube would use that one instead, but there isn't. Zube requires the same permissions as many other applications, the same permissions as Slack, for example.

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.

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

#69

Post by x0ner »

jenniferDewalt wrote: post #68
x0ner wrote: post #67

This looks really cool and is something I would love to check out, but the permissions of the actual app seem pretty high. For us, our code is stored in a private repository with no plan for any public release. Permissions for Zube are asking to not only read the private repository code, but also have write access to them as well. There's also requests to read/write web service hooks, deploy keys and pull requests. I…

We totally understand your concerns and we take security very seriously. In order to manage GitHub issues, GitHub currently requires the repo scope. If there was a more restrictive scope just for GitHub Issues, Zube would use that one instead, but there isn't. Zube requires the same permissions as many other applications, the same permissions as Slack, for example. On our side, Zube only accesses data related to your…

All that makes sense, thanks for the details.

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

#70

Post by x0ner »

jenniferDewalt wrote: post #68
x0ner wrote: post #67

This looks really cool and is something I would love to check out, but the permissions of the actual app seem pretty high. For us, our code is stored in a private repository with no plan for any public release. Permissions for Zube are asking to not only read the private repository code, but also have write access to them as well. There's also requests to read/write web service hooks, deploy keys and pull requests. I…

We totally understand your concerns and we take security very seriously. In order to manage GitHub issues, GitHub currently requires the repo scope. If there was a more restrictive scope just for GitHub Issues, Zube would use that one instead, but there isn't. Zube requires the same permissions as many other applications, the same permissions as Slack, for example. On our side, Zube only accesses data related to your…

All that makes sense, thanks for the details.
Post reply on HN