Overview
Use Search in the app header to find loaded Jira work by text, a supported field value or a link type, then select the results on the board. Search works locally with the loaded data; it does not run JQL or fetch additional issues from Jira.
Find the controls
Use Search in the app header. Its result panel contains individual matches and Select on board for the matching set; Include child issues changes the search scope.
The query returns eight Epic matches with child issues included.
Choose a result row for one work item, or the labelled selection action for the result set. These controls do not automatically open Inspector or turn on Focus.
Try a familiar work item
Try a simple search first: load a source, choose the planning level you need and type the key or a few summary words of a work item you recognise. Choose its result row, then open Inspector → Cards to check the selection. Once this works, try the combined field criteria shown below.
Try one result first
- In the example’s Story view, type Integrate KYC in Search.
- Read the result names and match explanations. Plain text ranks likely matches, so it can return more than one work item.
- Choose BAC-2, Integrate KYC vendor screening response mapping, rather than Select 2 on board. This selects just that result.
- Open Inspector → Cards. Check that its card count is 1 and its key is BAC-2.
Plain text ranks likely matches. Choose the result you recognise.
Choosing BAC-2 selects one card. Open Inspector to check its details.
Your source will have different work items. Use a familiar key or summary and check its identity in the same way. Search does not automatically open Inspector or turn on Focus.
Start with text or a field
Type an issue key, a summary fragment or a value from the supported fields. Text results are ranked by relevance, with exact issue-key matches prioritised.
For a more specific question, choose a field suggestion such as Status, which inserts status:. Then choose a suggested value from the loaded data to complete that criterion. Add another criterion after the first to narrow the question incrementally rather than replacing the query each time.
Status and Priority criteria narrow the Northstar results before selection on the board.
| Supported field | Example |
|---|---|
summary |
summary:payment |
status |
status:"In Progress" |
priority |
priority:High |
issuetype |
issuetype:Story |
project |
project:FRON |
assignee |
assignee:"Alice Smith" |
reporter |
reporter:"Sam Jones" |
labels |
labels:at-risk |
components |
components:Platform |
fixversions |
fixversions:"Release 4.0" |
storypoints |
storypoints:5 |
These are the supported search fields, not a promise to search every Jira field. Arbitrary custom fields, descriptions and comments are not supported search targets. Story Points is resolved from the site’s Jira field configuration.
Combine criteria
| Syntax | Meaning |
|---|---|
field:value |
Match a supported field value using case-insensitive, partial matching. |
link:typeName |
Match work participating in the specified Jira link type. |
| Plain text | Search issue keys, summaries and indexed field values. |
| Several field or link clauses | Require the clauses to match together (AND). |
Use quotes around values containing spaces. For example:
status:"In Progress"
status:"In Progress" labels:at-risk
status:"In Progress" labels:at-risk link:blocks
Choose suggestions as you build the query. A field suggestion inserts the field and colon; a value suggestion completes that criterion. Link suggestions help you discover link types available in the loaded work.
Note: Plain words rank likely matches rather than acting like strict combined Jira filters. Do not treat a mixture of free text and field clauses as a strict JQL-style AND expression. Use explicit field and link clauses when you need combined criteria.
Choose the hierarchy scope
Search follows the current planning level and offers two scopes:
| Scope | What matches |
|---|---|
| This level only | The current-level work item’s own indexed values. |
| Include child issues | A current-level work item can also match through its loaded descendants. |
Including child issues helps you find a parent because relevant work exists beneath it. It does not fetch missing Jira children. Review the match explanation to understand why a result is included.
Changing hierarchy level clears the search query. Choose the level you need, then enter the question for that level. Ordinary camera zoom is not a hierarchy-level change.
Select results on the board
Search returns at most 50 results. Narrow your criteria if you need a smaller working set. Selection acts on the returned results, not every possible match beyond that limit.
| Action | Result |
|---|---|
| Click a result, or press Enter on its highlighted row | Select that work item and bring its card into view. |
| ↑ / ↓ | Move through suggestions or results. |
| Select on board, or Cmd/Ctrl+Enter | Select the returned results on the canvas and frame the working set. |
| Escape while the dropdown is open | Close the dropdown first. |
| Escape again while Search remains focused | Clear the query. |
An Enter press on a suggestion inserts that field, link or value rather than selecting a card. Once you select results, open the Inspector to review the selection or explicitly enable Focus to isolate it. Search does not automatically turn on Focus.
Contextual help
Select the blue Help button, then hover over Search and click its highlighted region for an explanation without running the underlying action. See Guided Tours and Contextual Help.
Related
- Inspector: explain individual results and multi-selections.
- Semantic Zoom: choose the hierarchy level before searching.
- Focus Mode: isolate the selected working set.
- Guided Tours and Contextual Help: learn controls in place.



