7 ms·

Show HN: Trello for GitHub Issues

78 points by homeyer 13y ago

ragman55 13y ago
I'll definitely start using this!
dkordik 13y ago
Nice! Love the simplicity of it all!
Afforess 13y ago
Awesome, I am a trello fan. Too bad this didn't exist a year ago. Already migrated to JIRA because Github issues was so underpowered. I'd use it otherwise. :(
zhuzhuor 13y ago
thx, this is awesome!
bdcravens 13y ago
onclick on the "Go!" button is broken - it's incorrectly referencing the goToURL function as gotoURL. To get past it, use Enter on keyboard instead of the button. (Using jQuery, yet inline event definitions?)
- homeyer 13y ago
  fixed, thanks
aeden 13y ago
Does this work with private repos? If so then SHUT UP AND TAKE MY MONEY!
- mattvv 13y ago
  agreed... i hope it works with them soon!
- martindale 13y ago
  Seconded. I'd pay for this today.
- chadkruse 13y ago
  I'm a huge fan of this kind of business model: Public free/private pay. And if you do that, consider taking a page from the Sprint.ly playbook..only charge for months the user actually uses your service.
stenvoon 13y ago
Simplicity at its best. Thank you!
jashkenas 13y ago
Very nice. It's fun to look at Backbone.js' issues list from within a Backbone app ;) http://waffle.io/jashkenas/backbone http://waffle.io/jashkenas/backbone
- polysaturate 13y ago
  Javascriptception
shykes 13y ago
I'm going to test this right away for Docker. We are completely overwhelmed with github issues, and the bottleneck is not contributors: it's our ability to communicate where we need the most help.
- cheald 13y ago
  FWIW, issue labels can help this a lot. You can have a one-click link to a list of tagged issues, which helps to narrow the field a lot.
  - shykes 13y ago
    Tags do help. Our problem is the sheer volume of issues - 260 currently open and counting [1]. So prioritizing becomes an issue, as well as the unbarably slow web ui. [1] https://github.com/dotcloud/docker/issues?direction=desc&sort=created&state=open https://github.com/dotcloud/docker/issues?direction=desc&sor...
gry 13y ago
Also see http://huboard.com/ http://huboard.com/.
- zalew 13y ago
  similar: http://blog.bitbucket.org/2012/05/22/introducing-bitbucket-cards/ http://blog.bitbucket.org/2012/05/22/introducing-bitbucket-c...
- krallja 13y ago
  Application Error An error occurred in the application and your page could not be served. Please try again in a few moments. If you are the application owner, check your logs for details.
ntalbott 13y ago
Based on the email at the bottom of the page, looks like this is from the http://rallydev.com http://rallydev.com folks? I hope they have plans for an internal/private version, because while I'm not sure I'd use this for my open source projects, I'd love to try it for our internal repos.
- homeyer 13y ago
  It's built by a team of interns at Rally. We'd love to know why you'd use it for private repos but not open source projects, hoping to help people know where they can start contributing to an open source project.
  - mcrider 13y ago
    I think this could be used by staff that aren't familiar with github/scared of it (this is more common than you think) to manage issues in a simple and familiar way. I think it would certainly be helpful in my organization, but like GP our repos are private.
  - ntalbott 13y ago
    Having people know how to start contributing is not an issue I've had with my OSS projects; that could just be me though. Keeping straight what stage the Issues in our private repos are in, though - that's a very real problem I deal with every day. I'd love to be able to surface our internal company flow in a simple way like this; it's very kanban-like, and doesn't require us to add another tool or try to keep things in sync since it sits right on top of Github Issues which we already use.
troels 13y ago
Nice. Looks similar in design to the now defunct wallsome (Which used basecamp as the backend). Were you inspired by that?
sthulbourn 13y ago
I have this new system for "agile". You write everything down and then cross it out when it's done, continue until everything is done.
krallja 13y ago
http://waffle.io/rallysoftware/waffle.io http://waffle.io/rallysoftware/waffle.io: Application Error An error occurred in the application and your page could not be served. Please try again in a few moments. If you are the application owner, check your logs for details.
- homeyer 13y ago
  back up, sorry!

78 points by homeyer 13y ago

ragman55 13y ago

I'll definitely start using this!

dkordik 13y ago

Nice! Love the simplicity of it all!

Afforess 13y ago

Awesome, I am a trello fan. Too bad this didn't exist a year ago. Already migrated to JIRA because Github issues was so underpowered. I'd use it otherwise. :(

zhuzhuor 13y ago

thx, this is awesome!

bdcravens 13y ago

onclick on the "Go!" button is broken - it's incorrectly referencing the goToURL function as gotoURL. To get past it, use Enter on keyboard instead of the button. (Using jQuery, yet inline event definitions?)

homeyer 13y ago
fixed, thanks

aeden 13y ago

Does this work with private repos? If so then SHUT UP AND TAKE MY MONEY!

mattvv 13y ago
agreed... i hope it works with them soon!
martindale 13y ago
Seconded. I'd pay for this today.
chadkruse 13y ago
I'm a huge fan of this kind of business model: Public free/private pay. And if you do that, consider taking a page from the Sprint.ly playbook..only charge for months the user actually uses your service.

stenvoon 13y ago

Simplicity at its best. Thank you!

jashkenas 13y ago

Very nice. It's fun to look at Backbone.js' issues list from within a Backbone app ;) http://waffle.io/jashkenas/backbone http://waffle.io/jashkenas/backbone

polysaturate 13y ago
Javascriptception

shykes 13y ago

I'm going to test this right away for Docker. We are completely overwhelmed with github issues, and the bottleneck is not contributors: it's our ability to communicate where we need the most help.

cheald 13y ago
FWIW, issue labels can help this a lot. You can have a one-click link to a list of tagged issues, which helps to narrow the field a lot.
- shykes 13y ago
  Tags do help. Our problem is the sheer volume of issues - 260 currently open and counting [1]. So prioritizing becomes an issue, as well as the unbarably slow web ui. [1] https://github.com/dotcloud/docker/issues?direction=desc&sort=created&state=open https://github.com/dotcloud/docker/issues?direction=desc&sor...

gry 13y ago

Also see http://huboard.com/ http://huboard.com/.

zalew 13y ago
similar: http://blog.bitbucket.org/2012/05/22/introducing-bitbucket-cards/ http://blog.bitbucket.org/2012/05/22/introducing-bitbucket-c...
krallja 13y ago
Application Error An error occurred in the application and your page could not be served. Please try again in a few moments. If you are the application owner, check your logs for details.

ntalbott 13y ago

Based on the email at the bottom of the page, looks like this is from the http://rallydev.com http://rallydev.com folks? I hope they have plans for an internal/private version, because while I'm not sure I'd use this for my open source projects, I'd love to try it for our internal repos.

homeyer 13y ago
It's built by a team of interns at Rally. We'd love to know why you'd use it for private repos but not open source projects, hoping to help people know where they can start contributing to an open source project.
- mcrider 13y ago
  I think this could be used by staff that aren't familiar with github/scared of it (this is more common than you think) to manage issues in a simple and familiar way. I think it would certainly be helpful in my organization, but like GP our repos are private.
- ntalbott 13y ago
  Having people know how to start contributing is not an issue I've had with my OSS projects; that could just be me though. Keeping straight what stage the Issues in our private repos are in, though - that's a very real problem I deal with every day. I'd love to be able to surface our internal company flow in a simple way like this; it's very kanban-like, and doesn't require us to add another tool or try to keep things in sync since it sits right on top of Github Issues which we already use.

troels 13y ago

Nice. Looks similar in design to the now defunct wallsome (Which used basecamp as the backend). Were you inspired by that?

sthulbourn 13y ago

I have this new system for "agile". You write everything down and then cross it out when it's done, continue until everything is done.

krallja 13y ago

http://waffle.io/rallysoftware/waffle.io http://waffle.io/rallysoftware/waffle.io: Application Error An error occurred in the application and your page could not be served. Please try again in a few moments. If you are the application owner, check your logs for details.

homeyer 13y ago
back up, sorry!