Search and saved views
Ask for the exact slice of work.
Readable filters find issues by type, status, people, dates, fields and links. Save a search as a view, then use the same query for the list, a report and your AI agent.
Want to try it first? Build a query on sample data
- ACME-13Invite expiry date shown in UTCBug, Minor,
- ACME-12Invite link blank after it expiresBug, Major,
How the query reads
type: Bug- Only bugs. Separate values with a comma to accept either:
type: Bug, Task. #Unresolved- In any unresolved status, whatever each project calls it.
#Resolvedis the opposite. assignee: me- Assigned to whoever runs it. For Alex Lee that is
@alex; for an agent, the person who owns its token.
Clauses side by side must all match. Nothing is case-sensitive: type: bug is the same search.
From a question to a view the team reuses.
What high-priority bugs are still unassigned? Ask it once in the search bar, then keep the answer where the list, a report and an agent can all reach it. Pick a step.
- Show-stopper
- Critical
- Major
- Normal
- Minor
- -exclude value
Press ⇥ to complete the first item↵ runs the search
Choose Critical, Major and press Enter. Press / anywhere in the app to jump to this bar.
- ACME-7Burndown ignores late additionsBug, Critical,
- ACME-9Upload stalls at 100% on slow linksBug, Major,
Save this search as a view
- Name
- Unassigned urgent bugs
- Visible to
- Only youAppears in your tabs and sidebar; nobody else sees it.
- Everyone in a project(chosen)Every member of that project can use it and reference it as #{Name}.
- Everyone in the organisationEvery member of every project can use it.
- Project
- ACME
It keeps the query, the sort and the columns. Anyone in ACME can now write #{Unassigned urgent bugs} in a search, alone or with more filters.
Critical 1
- ACME-7Burndown ignores late additionsBug, Critical,
Major 1
- ACME-9Upload stalls at 100% on slow linksBug, Major,
Each group header counts the whole list, not only the rows on screen. Export CSV downloads the list as searched and sorted, up to 10,000 issues, with the columns you choose.
| Priority | Share | Issues |
|---|---|---|
| Critical | 1 | |
| Major | 1 |
Every bar opens the issue list with exactly the issues it counts. Change the view and the report follows, because it reads the view by name.
›What is in Unassigned urgent bugs today, and how does it split by priority?
- search_issuesquery: #{Unassigned urgent bugs}
- run_reportreport: issues-per-field, view: Unassigned urgent bugs, field: priority
Two bugs, both Open: ACME-7, Burndown ignores late additions, is Critical, and ACME-9, Upload stalls at 100% on slow links, is Major. One per priority, the same numbers as the chart.
Hand-drawn product views with fictional data. The agent reads through the same API and permissions as the app.
One query for the list, the report and your agent.
Change the filters on a sample project. The query, the matching issues, a name for the saved view, the report scope and the agent’s call all change together, because they are the same query. It runs in this page on fictional data; nothing is sent anywhere.
Type
Priority, any of
Status
Assignee
Pick @jordn to see what a misspelt value does.
- ACME-15Resend invite from the members listFeature, Normal,
- ACME-14Invite email subject names the orgTask, Normal,
- ACME-13Invite expiry date shown in UTCBug, Minor,
- ACME-12Invite link blank after it expiresBug, Major,
- ACME-11Swimlane header overlaps countBug, Normal,
- ACME-10Invite landing shows the inviterFeature, Normal,
- ACME-9Upload stalls at 100% on slow linksBug, Major,
- ACME-8Saved view count is staleBug, Normal,
- ACME-7Burndown ignores late additionsBug, Critical,
- ACME-6Project-scoped invite linksFeature, Major,
- ACME-5Accept invite while signed inBug, Major,
No issues match this query.
- Address
/issues?q=type%3A+Bug+%23Unresolved+assignee%3A+me- Saved view
- My open bugs · Only you ·
#{My open bugs}Nothing to save until the query is valid. - Report
- Issues per assignee
Issues per assignee for this query Alex Lee 2 Casey Kim 0 Sam Ortiz 0 Jordan 0 Unassigned 0 /reports/issues-per-assignee?q=type%3A+Bug+%23Unresolved+assignee%3A+meRefused with the same message and the same suggestions. - Agent
search_issuesquery: type: Bug #Unresolved assignee: me
Sample project ACME with eleven fictional issues. In the app the query runs when you press Enter.
Issues and articles, side by side, never mixed.
The search box at the top of the app answers in two groups: issues, and articles from your projects’ private knowledge bases. One tag reaches both, so the outage issues and the write-up taggedpayment-outage come back together.
When a query only makes sense for one kind, such as priority: High for issues orstatus: draft for articles, the other group says so instead of showing results.
Issues 2
- ACME-12Invite link blank after it expires
- ACME-6Project-scoped invite links
Articles 1
- ACMEInvitation links and expiry
The whole grammar fits on one page.
attribute: value, side by side for AND, commas or or for OR, parentheses to group, a minus to exclude, braces around spaces. Attributes cover people, dates, numbers, durations, links, custom fields and the sort order.
status: Open, Reopened-- either valuestatus: {In Progress}-- braces around a value with spacestag: -ui-- leave a value out#Critical-- a priority, status, type, tag or sprint by nameassignee: Unassigned-- nothing setdue date: Today .. {plus 14d}-- a date rangehas: -estimation-- not estimated yet"login redirect loop"-- a phrase in the title or descriptionseverity: High-- a custom field, by its slug(type: Bug or #Critical) assignee: me-- either side, groupedlinks: ACME-88-- linked to ACME-88 in any wayaggregate Parent for: {status: -Resolved}-- issues with an unresolved subtaskmentions: me-- issues that @mention you#{My open bugs} priority: Critical-- a saved view, narrowedsort by: priority asc, updated desc-- the order
Exact answers, only from work you can open.
A query either runs as written or is refused with a reason. Whatever it returns is limited to the projects the person, or the agent’s token, can open.
A typo is refused, with the fix beside it.
The part at fault is underlined, and the values that exist in the projects you can see appear beneath it as one-click replacements. An agent gets the same list back and corrects itself. Nothing is silently ignored, so a typo never looks like an empty result.
status: Donee → Donee is not a valid value for status.
Only projects you can open.
Jordan is a member of ACME but not of OPS. When Jordan searches #Unresolved, the answer comes from ACME alone: no OPS issue appears in the list, a group count, a report figure or an exported file, and autocomplete suggests only values from ACME. An agent’s token can narrow its projects further.
Views follow their definition.
Change a view and every search that names it follows. Delete it, and a search that still names it says so. Views can build on views: #{Open work} assignee: me works even when Open work is made from another view.
A saved view is a query, not a page.
A view keeps a query, its sort and its columns, for you, one project or the whole organisation. Knowledge base articles are documents, private to the members of their project, with a search of their own.
Questions about search.
How the query language, saved views and exports behave. The manual has every attribute.
Do we have to learn a query language first?
No. As you type, autocomplete offers attributes, values, saved views and recent searches, and Tab accepts the first suggestion. Words that are not filters search titles and descriptions. The syntax is there when you want precision, and the whole grammar fits on one manual page. Search manual
Is this semantic or AI search?
No. Filters match the names you see, such as statuses, people, tags and sprints, and free text is full-text search over titles and descriptions. Nothing is inferred, so a query means the same thing in the search bar, a report and an agent call.
Who can see a saved view?
You choose when you save it: only you, everyone who can open one project, or the whole organisation. Anyone can keep private views; Contributors and Project Admins can share one with their project; anyone who is a Contributor somewhere can share one with the organisation. Whoever runs a shared view still sees only issues in projects they can open.
Can we search custom fields?
Yes. Every custom field is an attribute named by its slug, such as severity: High or launch: {This month}, and its values follow the field’s type. Select options also answer the # shortcut, and the issue list can group by select, user and checkbox fields.
Can we export what a search finds?
Yes. Export to CSV downloads the list exactly as searched and sorted, up to 10,000 issues, with the columns you choose. A report exports the numbers on screen, and both leave out anything you could not open yourself.
How does an agent use search?
search_issues takes the same query as the search bar and returns a table. suggest_query gives the agent autocomplete, and search returns issues and articles in two groups, like the search box. Saved views are reachable by name, both as tools and as a view:// resource. MCP and AI agents
Ask your first question on real work.
Join the beta, create a project and type a query into the search bar. Save the ones you keep asking, and point your reports and your agent at them.