Opiniones de Shortcut

Limitado para gestionar incidencias

Puntos a favor:

Se configura rápido y es una alternativa a Jira

Puntos en contra:

Como se gestionan los ticket con puntuaciones

Developer-friendly and hits the Sweet Spot for Features

Puntos a favor:

Shortcut is "just right" for our needs, and thinking back about previous companies, would have been perfect in their needs, too. It is much more than a to-do tracker but doesn't overwhelm you with flexibility. My favorite part of this software is that it's story-centric. Epics are available, but they can play a supporting role if needed. Tasks are left to the developer to fill out themselves end up being merely a checklist. This paradigm shifts the focus to deliverables and prevents gamification by closing out menial tasks just to pump up ticket closures. As a bonus, this standardizes the language of Epics/Stories/Tasks. There is no more endless debate on what should be what. The one thing I've always seen with Jira, especially in young teams, is that the flexibility of the product creates unproductive debate and confusion about terminology.

Puntos en contra:

This product focuses on product delivery. For more general applications, like issue tracking or process management, it may not be the best for that.

Shortcut (previously Clubhouse) has been a great improvement for us.

Comentarios: Overall our experience has been great. Less has been falling through the cracks, and we're able to actively manage & prioritize our development with ease. The application is enjoyed by both the development team & the management team, so everyone is benefitting from our switch to Shortcut.

Puntos a favor:

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.

Puntos en contra:

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.

Short may be an overstatement for shortcut

Puntos a favor:

This is an adequate task management/tracking software. It has a fantastic Zendesk integration and multiple customizable fields. It also boasts decent search and filtering functions but it isn't particularly user-friendly and filling out all the fields that make it function well takes a great deal of time (hence the title of this review).

Puntos en contra:

There are no AI/smart suggestions for related epic/team fields so every time you make a new ticket you have to search through them by scratch. They also don't offer a great tag database or tag definitions so you have to create naming conventions separately offline. You also can't use rich text in story descriptions.

Effective Project Management for Small to Large Software Teams

Comentarios: I really enjoy using shortcut and it has given us the ability to manage complex projects. I highly recommend it.

Puntos a favor:

Whether you’re part of a small software team or you’re integrated into a collection of agile teams at an enterprise software shop - Shortcut makes it easy and intuitive to manage the many integrated software projects of todays micro services oriented development style. We’ve found that Shortcut grew with us from 2 devs to 10 and we expect it to grow with us as we grow to 50.

Puntos en contra:

Story management sometimes feels like a full time job, but at least Shortcut makes it a joy. For our open source projects we have a hard time integrating with issues on GitHub where public issues are generated, but for our private projects, the GitHub integration is lightweight and effective.

Scaled for the complexity of JIRA, but with the best UX possible & no sysadmins needed

Puntos a favor:

Every org grows out of Github Issues, Trello, and Asana when they realize a) stories need relationships such as blocking/blocked; b) stories need task checklists; c) different groups have different workflows; d) stories are often mini-project briefs and need to read as such. However, once you find yourself in JIRA, which you've been told is the mature platform for mature orgs, you're operating a nuclear submarine, you need 3 sysadmins, nobody can find anything, and you want to throw your computer out the window. SC has the infrastructure but with the user-friendliness of everyday software. Think of how Mixpanel took what Omniture was doing and made it accessible to the everyday marketer. That's what Shortcut does for eng/prod teams. No sysadmin needed, everyone gets it. Their API is well-documented and incredible. We do tons with Zapier because of how much they expose. Their CS team is spectacular, inquisitive, friendly, helpful. They want their customers to succeed. They have a one-click signup link which has made our onboarding process much faster They have templated stories and checklists which we use across the org for everything from product launches through onboarding/offboarding hires.

Puntos en contra:

very few dislikes. it's amazing. if i have to force criticism: - If you work cross-departmentally, avoid multiple workflows, or you'll be having to look at multiple kanban boards daily - the "dashboard" (home) isn't as useful as it seems like it should be so we all either use iterations or stories view for our daily lens - shortcut and productboard both boast integration, but it's not great, and i think this is the fault of productboard but really these criticisms represent like 5% negative compared to 95% enthusiastic positive

Took of our Trade

Comentarios: One spot for all teams to work together for client success is always going to be a win for a team.

Puntos a favor:

Shortcut does a great job allowing us to manage all facets of our product and being multiple teams together for what is most important, client and end user satisfaction. It follows standard agile flow but allows flexibility where engineers and non-engineers can use it alike. We also utilize their API for templates epics and stories and it is great to work with. Support team and client success managers have been a pleasure to work with when we’ve had conversations. They always are able to handle a situation or get us in touch with someone who can. Lastly the product is always evolving and they are very transparent through their website and slack channel of what is coming next to make your life better!

Puntos en contra:

Some things were less flexible such as naming conventions and required fields on stories/epics, but these are getting worked out over time (for ex projects are not required any more)

Clubhouse is all the software project management you need without the clutter and noise

Comentarios: Clubhouse has been a game-changer for us since we migrated from JIRA. We looked for something that was more lightweight, but still afforded us all the features we need to track our software projects. This is exactly what Clubhouse delivered, and more. I love the fact that Clubhouse gives you everything you need to track a project from the granularity of a sub-task, all the way up to milestones. This makes it easy to distinguish the forest from the trees, and present the relevant story to stakeholders at different levels. We haven't regretted the move to Clubhouse for a single moment, and we're always delighted with the new features that are regularly released. Simply put, Clubhouse gets out of your way very quickly and lets you get on with your actual goal: creating great software.

Puntos a favor:

- Clean user interface - Fast search - Continuously adding of new, useful features - Great integrations - Free for teams of up to 10 users

Puntos en contra:

- This is mostly me nitpicking, but I'd say reporting. It has been improving over time though. - It would also be great if there was a tool for simplifying backlog grooming

Shortcut (formerly Clubhouse) is a great task management tool for development teams

Puntos a favor:

Before switching to Shortcut, we used Jira. While Jira has plenty of features, we found it a bit cumbersome and the performance of the interface was atrocious (everything single task was incredibly slow, even the most basic activities had a noticeable delay). The first major benefit we saw with Shortcut was the speed of interaction - instead of waiting for the interface to catch up, we could just log in and get things done. The integrations with various source control platforms (we use the Gitlab integration) also helps keep task statuses up to date without even having to open the web interface. Overall the speed of the interface and the available integrations lead to a feeling that Shortcut never "gets in our way".

Puntos en contra:

We started out paying for Shortcut (when it was still called Clubhouse), but were soon switched to a free plan without even having to ask. Although this was a nice gesture on their part, they then released a beta of their new product called Write. This beta is only available for paying users, which is understandable, but having been moved to a free plan meant we couldn't access it. This isn't a major issue, but starting our subscription back up would require going through the approval process with our accounting department again so we've just stayed on the free plan without access to Write so far.

Shortcut is a great tool for small companies!

Puntos a favor:

Many of the features of this software are useful to our company. Our team has come to heavily rely on the roadmap view and reporting tools. These features have kept our company on track and increased our velocity in immeasurable ways.

Puntos en contra:

A few of the features our team feels are missing from Shortcut are custom fields and release management. If our team was able to have a reliable release management system, it would be very impactful to our team and customers.

Simple to use and provides enough features to run and manage sprints for a small team

Puntos a favor:

- Simple to learn and navigate so the team could quickly start using the product after switching- Love the dark mode and the colour coding of different story types i.e bug, feature or chore so it's easy to see things at the high level- Easy to create sprints and I like the summaries provided on the story points

Puntos en contra:

- You can only write stories in markdown text. Not a big issue since I've become really good at it! But it'd be good if there was a text editor instead- Sometimes when I create a story and I accidentally click out of it, I lose the progress. It'd be good if they had a draft functionality where the stories get created as a draft straight away

I've used Shortcut for everything for 3+ years

Comentarios: I use Shortcut to do everything in my job. I use it to write stories that engineers use to manage all of their work. My colleagues also submit requests, bugs, feature ideas, questions, etc. through Shortcut. Those turn into things for me to do, stories that get assigned to engineers, or just stories that the Product team uses to keep track of requests and help inform our roadmap + strategy.

Puntos a favor:

I manage engineering workflow as well as my own as an individual contributor in Shortcut. I also keep track of ideas and requests for when I set out to build new products. I love using labels in Shortcuts for managing my own workflow - requests that come from different teams get different labels so members of that team can see everything I'm working on for them and reliably know what state projects are in. I try to keep as much communication in Shortcut stories as opposed to emails because being able to reference it in Shortcut is very valuable to me. The search functionality is really good and unless I've named something really weirdly I can always find what I'm looking for.

Puntos en contra:

I haven't gotten familiar with using notifications in Shortcut and I rely on email notifications. This isn't to say that Shortcut doesn't have the right capabilities for notifications (commenting on stories is what I want notifications about), but just that I haven't really explored/figured it out which says something itself.

Previously Clubhouse, Shortcut really did cut our processes shorter.

Puntos a favor:

1) Easy to learn - Even our junior members got on-boarded quickly despite their absolute lack of familiarity to such tools. 2) Tons of tagging options - Tickets can get multiple labels and the long list of standard metadata for cross-posting and maximum searchability. 3) Powerful search box - We get lots of tickets using the same set of keywords yet the search function seems to algorithmically know exactly which one we are looking for!

Puntos en contra:

1) Comment formatting is not WYSIWYG 2) A bit pricey for smaller teams 3) Continuous development is great, but there's always a new key feature deployed quickly that will make you rethink your currently-established conventions. We found ourselves testing these, and even migrating to fully commit to using the new feature instead (e.g. milestone-centric vs iteration-centric). There's this unshakeable worry that there's a new feature yet again right around the corner and we may have to switch once more.

I'm a fan of shortcut

Puntos a favor:

Epics, millestones, projects, tags, workflow and reports are awesome!! The plataform is very intuitive and make understanding easy. The atualizantions aways come with great news and features

Puntos en contra:

My team is not from the technology business so some features doesnt make sense to us. My team speak portuguese, so the language sometime is an difficult point for some. Losing the story's interactions history makes my team use the tags to identify the sprints.

While it does the job, it's not easy to use for sorting or management

Comentarios: I am only a user, but I know that our Engineering manager will be switching us to a different product soon for ticket management with the reason that the new product will be much easier for everyone to use - especially for tracking their own tickets.

Puntos a favor:

Does what we need it to do - create bug tickets

Puntos en contra:

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.

Exactly what we need

Comentarios: It is the best tool for our business given our current size. I would recommend it for small teams of designers and engineers. Its integration with GitHub and similar tools is best in class.

Puntos a favor:

Its interface is super fast compared to tools like Jira. I find the platform extremely easy to use and configure.

Puntos en contra:

The interface has changed recently and at times that can be jarring. But I have no major complaints.

Shortcut Review

Puntos a favor:

Shortcut is a project management tool which is very easy to use and is suitable for agile teams. It also integrates with a lot of third-party tools, e.g. Slack, which works just fine and is helpful.

Puntos en contra:

I didn't find any disadvantages in particular. However, the free plan is unfortunately (but unsurprisingly) quite limited.

Clubhouse is the Goldie Locks Level of JUST RIGHT!

Comentarios: When I started at this company they had no real process and no project management. They were using a collection of about 70 Trello boards to categorize and track work, but there was no roll up view of everything and the sheer flexibility of Trello was too much to manage. I have worked in JIRA and similar platforms before, they are cumbersome to set up and require that you utilize their entire eco-system for more rich-features. Clubhouse is the perfect middle ground. It helps us organize our 6 teams and their workloads, prioritize work among the many company priorities and work with the owners to come up with roadmaps for the future... ALL IN THE SAME TOOL! As we are able to build in our branching and deployment process into Clubhouse, it will be even better for us. We are truly working toward standardizing our work items, planning and estimating and could not have done that without Clubhouse.

Puntos a favor:

I like the ease of use, from day one of setting up Clubhouse it just made sense and was easy to configure for our purposes. It was easy to jump in and start using without much learning curve for all of the team members as well. We love how much work we can have in a single work space and with powerful filtering, searching, everyone gets their perfect view for their purpose!

Puntos en contra:

I wish there were more canned reporting features for Kanban workflows, but honestly it's not the end of the world since we have access to the REST API for building our own custom reports! Right now our private Gitlab integration isn't working but what is amazing is that Clubhouse support and engineering is working through it with us. I love that about Clubhouse. (Can you tell it's hard for me to find something negative about the software???)

Lots of different features, adaptable to individual needs

Comentarios: Has worked well to track the many things going on, ensure accountability and meet our fast-paced start-up team's needs.

Puntos a favor:

Works as expected for an agile project management software; lots of different ways to add granularity (or not) depending on the team's needs. I use it a bit differently when interfacing with PMs vs. developers, and it works well for both. There are a variety of ways to label, flag, track, and segment tasks so it can fit most needs.

Puntos en contra:

Due to all the customizability, understanding the views and different flags and how they interact can take time. For example, a "team" category may be selected but not a "project" category, so then a task may not show up in a given view. This is ok so long as your team knows what they are looking for and things are assigned appropriately.

Enhance Report Feature and Empty Seat Charges

Puntos a favor:

Can branch out the epic easily from origin when too much topic / stories relate to one single task, easy to manage.

Puntos en contra:

Report : difficult to view milestone and every team member epic / stories completion, declared start and end date vs actual end date.Charging fee : I have team member join and leave, empty seat is a waste of money.

Great Product

Comentarios: Fantastic, it's very straight forward and easy to use within a small dev team (about 30)

Puntos a favor:

It's non-invasive product that can be used in many different development processing styles, we have used it from Scrum, to KanBan to ShapeUp

Puntos en contra:

Tasks/Ideas can easily get lost due to poor organization of shortcut

Best project management tool, period

Puntos a favor:

Fast. Easy to onboard. Easy to use.Clear

Puntos en contra:

I like everything, even that one day their team called us to hear us out

A perfect balance between the complexity of JIRA and the looseness of Trello

Comentarios: Years ago we started with JIRA, it did the job, but was so complex to administrate that we could not adjust and reaccess our process as we learned and grew. So we moved to Trello. Trello allowed a large amount of freedom to try new ideas on how we work. However, in the end, it was frustrating that Trello did not understand what software development was, and we had to rely on hacks to get proper reporting and insights. That led us to Clubhouse, which is a nice happy medium. It is opinionated on what software development looks like, but it gives just the right amount of flexibility so we can adjust as needed.

Puntos a favor:

* It embraces the modern development process * It's fast and responsive * Almost all you need is in one screen * It has multiple layers of organization (story, epic, milestone)

Puntos en contra:

* The higher layers of organization do not 100% align with our process * Some features are not available on different layers and it seems arbitrary. For example, you can't get a burn down on a sprint if that Sprint is not tracked as a "milestone". So if you are using Milestones to track large scale projects (maybe quarter goals or multi-epic initiatives) you have no way to track how your Sprint is going. Either they need a first-class Sprint concept, or allow burn downs on labels.

Lots can be improved

Comentarios: It was a tough transition coming from a different company that used JIRA. JIRA is harder to learn but it is way more powerful. Shortcut needs a lot more customization but in a user-friendly way that keeps its simplicity.

Puntos a favor:

Simpler to use than JIRA since the defaults are good enough for most cases.

Puntos en contra:

Cannot find documentation. Googling clubhouse or shortcut leads to completely wrong products. The product name is not unique enough / does not have enough SEO to find help on Google. Custom search is not powerful enough. I really like JIRA's JQL where I can write arbitrary search filters and sort bys. In fact, I can't even sort when using the search filters! It always sorts by relevance but if I need to groom the backlog, I can't even sort by ticket creation time or ticket number.

Clubhouse is the best in class for bug and issue tracking

Comentarios: Clubhouse replaced a number of other issue tracking tools that were of lesser quality and far more clunky to use. I enjoy using Clubhouse more than many other tools, including Trello.

Puntos a favor:

Clubhouse has a modern UI that feels fast. Search is very powerful and you can usually find past issues that you are looking for without a great deal of work.

Puntos en contra:

The Clubhouse APIs are relatively new and while they are good, they do not cover everything you might need to do. The integrations with Slack are OK and maturing.