User guide

Search, filters, and export

Two ways to find things: reach for the search box when you are looking for one thing, and build a saved filter when you keep asking the same question. This page covers both, plus the honest limits of each.

⌘K / Ctrl+K from anywhere a JQL-lite grammar CSV that opens clean in a spreadsheet

The search bar in the navigation - or ⌘K (Ctrl+K on Windows and Linux) - opens an overlay over any page. One box searches work, projects, and collaboration: type a title, a reference like ENG-1, or a phrase in quotes to match it exactly. Alongside the matches the overlay offers two kinds of shortcut:

  • Filters - your organization's saved filters appear as you type; choosing one runs it instead of searching.
  • Commands - when your query finds a project you can file into, the results carry New work item in <Project>, up to three of them. The row is the permission check: the command is built from projects you may actually create in, so it never offers a dead end.

Pressing Enter opens the full search page, where results split into work and messages with their own filters: Scope, Assignee, and for conversations Message author, Messages from and Messages to. Long result sets page with Load more results.

Saved filters

A saved filter is a named question you can re-run. The Dashboard is where they live - reach it with the Dashboard button at the top of the Work page, which opens your primary organization's board of filters (if you belong to several, pills across the top switch between them). New saved filter starts the form, which asks four things:

  • Name - what the question is called.
  • Start from - Every work item I can see or Assigned to me: the universe before any conditions.
  • Who can run it - Only me, or Everyone in this organization. A shared filter runs inside the organization's boundary but each person still only ever sees the work they are allowed to see - sharing a filter never shares access.
  • Only work that needs my attention - the same switch as on the Work page, as a condition.

The filter's own page runs it, pages through the answers, and offers Export CSV, Edit and Delete; the dashboard shows your filters as widgets, so the morning routine is one page.

The query grammar

The Query box takes a sentence that compiles into the filter's stored conditions:

project = IMP AND status != Done AND priority in (high, lowest) AND due = overdue AND assignee = me

Eight fields are writable, and the error message names them when you use a ninth:

FieldTakes
projectproject keys or names
statusyour organization's status codes or display names
typework item types, built-in or custom
prioritypriority codes
labellabel slugs
duebuckets: overdue, today, next_7_days, none
assigneea username, or me
needs_attentiontrue / false

Operators are =, != and in (a, b), joined by AND. Names and codes both parse, because status != Done is a sentence a person writes, and someone who knows the code can type that instead.

What it refuses, and why

The grammar says no out loud rather than returning an empty list:

  • No OR. "A saved filter stores one list per field, so it cannot express OR - use two filters instead." One question per filter keeps the answer explainable.
  • No date comparisons. due holds buckets (overdue, today, next 7 days, none), not ranges - the stored condition is a shelf, not a calculator.
  • No invented fields. Anything outside the eight gets an error that lists what is allowed.

Two subtleties make the whole thing trustworthy. != is resolved at save time against the organization's active workflow: the filter stores the explicit list it computed, the chips show exactly which statuses it will match, and a status added next week is not silently pulled into yesterday's "not Done". And the query is an input, not a second truth - the stored conditions are the record, and the canonical sentence is regenerated from them, so the words and the data can never disagree.

Export

Every result page has an Export CSV button that copies what you are looking at - the backlog, the board, a saved filter - with the same filters applied. Each row carries the reference, name, parent, type, status, priority, labels, assignee, iteration, project, story points and dates, plus a link back to the item; every organization-configured word (status names, type labels) comes through in the organization's own vocabulary. Text cells are neutralized against spreadsheet formula injection, so the file opens safe, not clever.

Keep going