Shortcut
Shortcut Project Management Review and Pricing: Stories and Iterations
Shortcut project management gives product and engineering teams Stories, Epics and Iterations for organizing delivery. A team can collect the smaller pieces of work under a larger objective, plan a timeboxed iteration and connect Story progress to GitHub activity.
The appeal is a dedicated software-planning workflow with code-driven updates and an actual small-team free option. Start by inspecting how one of your features would break into Stories and move through an iteration.
Stories can follow development activity
The GitHub connection attaches commits, branches and pull requests to Stories. Configured events such as pull-request opening, review activity or branch merging can change Story state. Branch formatting and event handlers matter: the team must decide which code events mean that a planning status should change.
For example, review approval and merging can represent different steps in your workflow. Map them accordingly rather than equating a code event with delivery to users.
Shortcut pricing: Free, Team and Business planning
Shortcut pricing lists Free for ten users with one team, workspace and workflow, plus Stories, Epics, Iterations, docs and selected integrations. That gives a small team room to assess real planning, provided one workflow is sufficient.
Team adds multiple workflows, work-in-progress limits, automation and all integrations. Business adds strategic objectives, advanced fields and reporting, and multiple workspaces. Check the pricing page for up-to-date per-user amounts in your currency and billing term. Enterprise is quoted, with SSO/SCIM, support SLAs and onboarding. Confirm monthly terms separately if annual billing is unsuitable.
Observer access is paid-plan-only, capped at five Observers per paid seat according to current role documentation. Free lacks Member and Observer roles. The fourteen-day trial's broader allowances should not be treated as permanent free collaboration rights; check the actual permissions needed by stakeholders and contractors.
If switching from Jira, choose import or ongoing sync
The Jira importer maps epics to epics and subtasks to Stories with a parent dependency. It requires administrator access in both tools. Repeating an import creates duplicate Stories unless it is rolled back, so an import rehearsal needs a controlled reset plan.
Ongoing Jira Sync behaves differently. It creates records in both directions and synchronizes titles and descriptions, but state changes travel from Shortcut to Jira without the reverse state update, and most metadata changes are not synchronized. Only one Jira Sync can be active per workspace. Those limits matter if you expect teams to work interchangeably in both tools.
CSV migration uses a support request and template flow. Confirm the transfer process and required history before booking the move. If self-hosting is mandatory, compare the buyer-operated options in our self-hosted guide.
Alternatives and the next step
Linear offers issues and cycles with GitHub status automation and different paid-access boundaries. Jira is worth retaining in the comparison when configurable processes and wider planning are central. The software-team comparison helps frame that choice.
Evaluate Shortcut with a feature, its Stories and one GitHub state change. If switching from Jira, add a difficult import record and verify sync direction before agreeing a cutover. That is a more useful buying check than relying on the trial's maximum allowances.