RIP JQL: How to Find Your "Open Sprints" in a Linear World
- The Shock: Linear has no JQL. You cannot type sprint in openSprints() to find your work.
- The Fix: Linear replaces "Search Queries" with "Context Views." You browse by context (Cycle, Project, Team) rather than filtering a massive database.
- The Shortcut: Cmd+K (or Ctrl+K) is your new JQL. It is the command center for navigating to any view instantly.
- The Philosophy: Jira asks "What specific tickets match this criteria?" Linear asks "What are we working on right now?"
For power users, the hardest part of leaving Jira isn't the migration itself; it's the muscle memory. You have spent years mastering JQL (Jira Query Language). You know exactly how to type assignee = currentUser() AND resolution = Unresolved to see your dashboard.
Then you open Linear, look for the "Advanced Search" bar, and... it's gone. Panic sets in. "Where is my backlog? How do I filter for high-priority bugs?"
This guide is your translation layer. We will map your favorite Jira habits to Linear's "Maker" philosophy.
If you are still deciding whether to switch, make sure to read our comparison on Jira vs. Linear 2026: The "Speed vs. Control" War Is Over to understand the performance benefits you are gaining in exchange for this learning curve.
The Mental Shift: Querying vs. Browsing
Jira is essentially a massive database with a UI slapped on top. Every time you want to see work, you are technically running a database query. This provides infinite flexibility but requires high cognitive load.
Linear is an opinionated workflow engine. It assumes that 90% of the time, you want to see one of three things:
- What am I supposed to do? (My Issues)
- What is the team doing this week? (Current Cycle)
- What is the status of this big feature? (Project)
Because these views are pre-baked, you don't need JQL to find them. They are default navigation items.
The Translation Dictionary: Jira to Linear
Here is exactly how to replicate your most common JQL queries in Linear.
| Jira JQL Query | Linear Equivalent | How to Access |
|---|---|---|
| sprint in openSprints() | Current Cycle | Click on your Team Name > "Cycles" > "Active". Or press G then C. |
| assignee = currentUser() | My Issues | Top left sidebar "My Issues". This view aggregates your work across ALL teams. |
| project = "WEB" AND type = Bug | Team Filters | Go to the Team, press F (Filter), and select "Bug". |
| text ~ "login error" | Cmd+K Search | Press Cmd+K and just type "login error". It searches globally. |
Sprints vs. Cycles: The "Start/Stop" Button is Gone
In Jira, a Sprint is a container you manually create, start, and complete. If you forget to click "Complete Sprint," your reports get messed up.
In Linear, Cycles happen automatically. You set a cadence (e.g., 2 weeks). When the time is up, the cycle ends. Unfinished work automatically rolls over to the next cycle (or the backlog, depending on your settings).
This "Auto-Rollover" feature terrifies Scrum Masters at first, but developers love it. It removes the administrative overhead of "Closing the Sprint."
Pro Tip: You cannot name cycles "Sprint 42" easily. Linear names them "Cycle 24". You need to let go of the specific naming conventions and trust the dates.
Rebuilding "Advanced" Filters with Views
But what if you need a complex view? Say, "All High Priority Bugs assigned to Junior Devs created last week"?
For this, Linear has Custom Views. You can create a personal view using a visual filter builder (no code required). Once created, this View sits in your sidebar just like a Jira Filter Subscription.
However, you cannot use logic like `(A OR B) AND (C OR D)` as deeply as JQL. If you need that level of boolean complexity, you might be over-engineering your process.
Frequently Asked Questions (FAQ)
It is now called "Current Cycle". You can find it under your Team name in the sidebar, or simply by pressing the shortcut G then C (Go to Cycle).
You don't. Linear does not support a text-based query language. You use the visual "Filter" menu (shortcut: F) or create "Custom Views" for saved searches.
Sprints are manual; Cycles are automated. Cycles run on a fixed schedule (e.g., 2 weeks) and automatically roll over unfinished work, whereas Sprints require a manual "Start" and "Complete" action by a manager.
Linear provides a default view called "My Issues" at the top of the sidebar. This view intelligently aggregates every ticket assigned to you from every team you belong to.