home / skills / thebushidocollective / han / search

search skill

safe

/plugins/services/jira/skills/search

This skill helps you search Jira tickets by JQL or text, returning concise results and tips to refine queries.

npx playbooks add skill thebushidocollective/han --skill search

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.1 KB

---
name: search
description: Search for Jira tickets using JQL or text
---

# search

## Name

jira:search - Search for Jira tickets using JQL or text

## Synopsis

```
/search [arguments]
```

## Description

Search for Jira tickets using JQL or text

## Implementation

Search for Jira tickets using either JQL (Jira Query Language) or simple text search.

**Usage**:

- `/search authentication bug` (simple text search)
- `/search project = PROJ AND status = "In Progress"` (JQL query)

Use the Atlassian MCP tool `atlassian_search_issues`.

**Logic**:

1. If the query contains JQL operators (=, AND, OR, IN, etc.), use it as JQL directly
2. Otherwise, construct a JQL query that searches across:
   - summary ~ "query"
   - description ~ "query"
   - comment ~ "query"

Display results in table format:

| Key | Summary | Status | Assignee | Priority | Updated |
|-----|---------|--------|----------|----------|---------|

Limit to 20 results. If more exist, show: "Showing 20 of X results. Refine your search for more specific results."

Provide helpful JQL tips if search returns no results.

Overview

This skill lets you search Jira tickets using either JQL (Jira Query Language) or simple text queries. It runs queries through the Atlassian MCP search tool and returns a concise table of matching issues, including key fields like status, assignee, priority, and last updated. Results are limited to 20 items with messaging when more matches exist.

How this skill works

If your input contains JQL operators (for example =, AND, OR, IN), the skill treats the input as a JQL expression and runs it directly. For plain text queries, the skill builds a JQL that searches summary, description, and comments for the text. It formats matching issues into a compact table and adds guidance when no results are found.

When to use it

Quickly find tickets by precise JQL expressions (project, status, labels, components).
Search across summaries, descriptions, and comments using natural language phrases.
Audit or review recent work by sorting/filtering with JQL and checking key fields.
Investigate assigned work or high-priority items without opening Jira UI.
Validate whether a bug or feature exists before creating duplicate tickets.

Best practices

Use explicit JQL for exact filters (project = PROJ AND status = "In Progress") to reduce noisy results.
For broader searches, keep text queries to 2–4 words that capture key terms or error codes.
If you get many results, refine by adding project, status, assignee, or date constraints.
When no results appear, try alternative keywords, synonyms, or expand/relax quoted phrases.
Limit heavy queries during peak times; complex JQL with many ORs can be slow.

Example use cases

/search project = PROJ AND priority = High AND updated >= -7d — find high-priority work updated in the last week.
/search authentication bug — text search across summary, description, and comments for mentions of an authentication bug.
/search assignee = alice AND status != Done — list Alice’s open work for quick standup prep.
/search project = OPS AND labels IN (outage, incident) — track recent incident tickets for postmortem.

FAQ

What if I see more than 20 results?

The skill shows the first 20 results and a message like "Showing 20 of X results. Refine your search for more specific results." Use additional JQL filters to narrow results.

How do I force a JQL search?

Include JQL operators (for example =, AND, OR, IN) in your query. If operators are detected, the input is run as JQL exactly as written.

What if my text search returns no results?

Try alternative keywords, remove quotes, broaden or shorten the phrase, or switch to explicit JQL with project/status constraints for targeted searching.