We recently started using Clubhouse after using GitHub Issues for about two years. As a dev team, GH Issues was pretty much perfect for what we needed - we used the Projects feature at an Org Level to track issues across multiple repositories in each of our sprints. However the lack of visibility for non-devs was an issue - and we found that adding non-devs to our GitHub org didn't work so smoothly and we ended up with a lack of clarity on priority.
I wouldn't say Clubhouse is perfect but it feels like they are getting there. One area that needs a bit of work is their UI around iterations/sprints - they have some super flexible views and filters but the navigation to get there isn't always super obvious. They've been advertising pretty heavily recently and it seems like they are anchoring on two things:
Anti-JIRA: they are pitching themselves as offering the power and flexibility of JIRA without the hot mess that often ensues. For me, they offer a well-configured default that will work for most small dev teams and startups. That said, don't expect anywhere close to the configurability of JIRA for your workflows. For us that's a good thing, but YMMV depending on what you're looking for.
"Beautiful UI": Personally I think their UI is good but I think it lacks a little polish, especially on the mobile app. A decent designer would take their UI from good to great in no time. I'd love to see it get the Steve Schoger treatment as I think some subtle improvements would take it a long way.
One of the very nice things about Clubhouse is that they recently made it free for up to 10 users. For small companies like us, this means you can get most of your team using Clubhouse and see if it works for you before you pay a cent.
Before we opted to use Clubhouse we tried and evaluated a number of other similar products - but in the end we felt Clubhouse had the best combination of power and simplicity. Overall, I'm happy with the decision we made and I'm confident Clubhouse will only get better in the future.
We recently started using Clubhouse after using GitHub Issues for about two years. As a dev team, GH Issues was pretty much perfect for what we needed - we used the Projects feature at an Org Level to track issues across multiple repositories in each of our sprints. However the lack of visibility for non-devs was an issue - and we found that adding non-devs to our GitHub org didn't work so smoothly and we ended up with a lack of clarity on priority.
I wouldn't say Clubhouse is perfect but it feels like they are getting there. One area that needs a bit of work is their UI around iterations/sprints - they have some super flexible views and filters but the navigation to get there isn't always super obvious. They've been advertising pretty heavily recently and it seems like they are anchoring on two things:
Anti-JIRA: they are pitching themselves as offering the power and flexibility of JIRA without the hot mess that often ensues. For me, they offer a well-configured default that will work for most small dev teams and startups. That said, don't expect anywhere close to the configurability of JIRA for your workflows. For us that's a good thing, but YMMV depending on what you're looking for.
"Beautiful UI": Personally I think their UI is good but I think it lacks a little polish, especially on the mobile app. A decent designer would take their UI from good to great in no time. I'd love to see it get the Steve Schoger treatment as I think some subtle improvements would take it a long way.
One of the very nice things about Clubhouse is that they recently made it free for up to 10 users. For small companies like us, this means you can get most of your team using Clubhouse and see if it works for you before you pay a cent.
Before we opted to use Clubhouse we tried and evaluated a number of other similar products - but in the end we felt Clubhouse had the best combination of power and simplicity. Overall, I'm happy with the decision we made and I'm confident Clubhouse will only get better in the future.
Great context, thanks Joe!