Per-App Search: Jira
Facets for project, priority, assignee, and sprint
You'll be able to
- Scope a query to Jira and filter by project and priority
- Combine assignee and sprint facets to surface the right work item
Read first
Day 3 Lab
- Run
app:jira project:plus a project key. Note how much it narrows. - Add
priority:highto keep only the urgent items. - Add
assignee:to scope to one person. - Add
sprint:to limit to the current iteration, then read the count.
Working Example: Jira Facets
Jira indexes work items by structured fields; app:jira selects the source and each facet matches a Jira field. Verified against datasource_filters.
app:jira project:ATLAS
→ every Atlas ticket — too broad
app:jira project:ATLAS priority:high assignee:@raj
→ only Raj's high-priority Atlas tickets
app:jira project:ATLAS sprint:"Sprint 7" priority:high
→ high-priority Atlas tickets in the current sprint — a standup-ready listLead with project: because it is the highest-cardinality split in most Jira instances — one facet drops you from the whole backlog to one team's board, and every facet after that refines a much smaller set. Verified against datasource_filters.
Check for understanding
Why is project: usually the first Jira facet to add?
Check yourself
1. What does a built-in Glean Skill bundle together?
2. In a busy Slack channel, which facet pair pins a message fastest?
3. What does `app:jira project:ATLAS priority:high assignee:@raj` return?
4. Why does a Confluence `label:` facet help you find the canonical page?
5. Which Salesforce facets together build a 'large deals closing this quarter' shortlist?
In 10 seconds
“Jira speaks in project, priority, assignee, sprint. app:jira project:ATLAS priority:high assignee:@raj finds Raj's urgent Atlas tickets without leaving search. Lead with project — it scopes the noise away first.”
Per-App Search: Confluence