Search a lens
Search scans the visible lens for text matches and highlights every hit. Use it when you have hundreds of rows and need to find a specific issue, assignee, or keyword fast without rebuilding a filter.
Search matches on the Summary field by default and keeps the hierarchy intact — matching rows and their parents stay visible so you never lose context.
Run a search
Section titled “Run a search”- Click into the search box in the toolbar, or press the keyboard shortcut to focus it.
- Type a term. Foundation matches prefixes on every word, in any order, so
login pagefinds both “Page for login” and “Login page redesign”. - Watch the match badge: it reads 1 / 12 matches once the query resolves.
- Press Enter to jump to the next match. Press Shift+Enter to jump to the previous one. The grid scrolls to keep the active hit on screen.
- Press Escape or click the x inside the search box to clear the search and restore the full view.
Narrow a search further
Section titled “Narrow a search further”- Combine with Quick Filters to scope results (for example, “My issues” + search for “billing”).
- Combine with Quick Groups to cluster matches by status, assignee, or sprint.
- Switch to another view if you only need the search against a specific column set.
What search matches
Section titled “What search matches”- Issue summary text (prefix match on each word, case-insensitive).
- All words must be present — word order does not matter.
- Parent rows of a match stay visible so the tree structure is readable.
Search is per-session and per-user. It does not modify the lens, the view, or what other users see.
- Keep queries short. Two or three words usually find the right issue faster than one long phrase.
- If a match count is zero, check whether a Quick Filter or the active view is hiding the row you expected.
- For power queries over Jira metadata (status, sprint, labels, assignee), use a Pipeline Studio filter or a Sync Agent instead of search.