Shortcut

Clubhouse brought us a new set of features and ways to organize stories and tasks that we didn't know we wanted/needed. We have always stuck with tools that were able to help improve our kanban based workflow rather than the simple project board tools like Trello that cater to everyone more than software/product development specifically.

There are few tools out there that provide what we are looking for: the ability to organize and label stories with more granularity than a single label (estimates, types, project, priorities, epic, etc), and the ability to have reports like velocity and burndown charts.

It is a very small thing, but it would be nice if we could adjust the color scheme of both things like labels beyond the default options, as well as adjust the overall interface colors.

1. The app is very easy to configure & set up.
2. The user experience is seamless & functionality is very self-explanatory.
3. There are multiple ways to configure each component, so you can set up the app according to what works best for you & your company. (No "one size fits all" model.)
4. The ability to set up different workflows for different departments has been a huge help for us.

1. It's a little hard to envision how each of the components should be set up for your organization when you're first getting in there (i.e., projects, workflows, milestones, epics, stories), so we ended up changing the setup as we went along after the initial configuration. This wasn't necessarily a bad thing, as it allowed us to improve the way we currently did things.
2. The biggest issue we have now, after using the app for a while, is that stories do not populate into the Gantt charts, only epics. This means if we have one-off tasks that are added as stories, those do not pull into the report we'd like. For that reason, we have to set up an entire epic just to set up a single story, for reporting purposes. I think it would be great if you had the option to pull the Gantt reports at the epic or story-level.

Does what we need it to do - create bug tickets

Not easy to filter, find or sort. Maybe I just don't know how to use the features, and I know I use them in a completely different fashion than Engineering does (we create tickets, they execute them), but each time someone says "just filter and find", I have no idea and can't figure it out. I also hear from their team about how hard it is to do what they need to do with the tickets once we create them. Not user friendly for sorting or tagging for projects.