Searching Issues

Searching Issues

Search is the request teams make most, partly because it is read-only: it never needs approval and runs the same way in every autonomy mode.

Asking in Plain Language

@Quickly show open bugs in MOBILE
@Quickly what High priority issues are unassigned?
@Quickly list everything assigned to me that is still open
@Quickly what changed on PROJ-123 this week?

Quickly translates the request into a JQL query and runs it against your Jira. Because it uses your connection, you only ever see issues your own account can see.

Looking Up One Issue

@Quickly what is the status of PROJ-123?

A single-issue lookup returns the current state: summary, status, assignee, priority, and a link. Use it before a standup rather than opening the tracker.

Narrowing the Search

The more specific the question, the more usable the answer:

• By project — "in MOBILE", "across MOBILE and API"
• By status — "open", "in progress", "resolved this week"
• By assignee — "assigned to me", "unassigned", "assigned to sarah@example.com"
• By priority — "High and above", "Lowest priority"
• By time — "created since Monday", "updated in the last 24 hours"

Result Size

Searches return ten issues by default. Ask for more when you need a fuller picture:

@Quickly show the 25 oldest open bugs in MOBILE

Large result sets are summarized rather than dumped in full. If you need every row, ask Quickly to write the results somewhere you can work with them, such as a page or a table.

Writing JQL Directly

If you already know JQL, you can hand it over:

@Quickly run this JQL: project = MOBILE AND status = "In Progress" AND priority in (High, Highest)

A query needs a real restriction. A bare ORDER BY with no filter is rejected, because it would try to read the entire instance.

Turning a Search Into Something Else

Searches compose with the rest of what Quickly does:

@Quickly summarize the open High priority bugs in MOBILE and post it here
@Quickly find the unresolved incidents from last week and draft a summary page in the ENG space

Making It Recurring

A search you run every Monday is a playbook waiting to happen. Saving it means it runs on a schedule and posts results to the channel that needs them, without anyone remembering to ask. See Understanding Playbooks.

When Results Look Wrong

If a search returns less than you expect, the usual cause is access rather than the query. Quickly can only see what your Jira account can see, so a project you were removed from disappears from results. Action Logs shows the exact JQL that ran, which makes the difference between a bad query and a permissions gap obvious.