If the atlassian cli (acli) is available, use it to search for relevant Jira issues and view historical context.

If the acli command line tool is not available, simply respond that you cannot interact with Jira.

Searching and Viewing

• Search for work items using the jql query language: acli jira workitem search --jql 'text ~ "search-term"'
• View a given work item by key: acli jira workitem view PROJECT-123

Look at the current branch name. If the current git branch name begins with a jira issue reference (i.e., a branch name of PROJECT-123/fix-bug is related to Jira issue PROJECT-123), start by viewing that Jira work item since that is the work item that is being worked on currently.

Consider the parent work items of the relevant work items and if it would be helpful, indicate which relevant work items are under the same parent since they are likely related. Also indicate the date these work items were developed in your response, since that indicates how relevant the information in the work item may be.

IMPORTANT

Your response should include ALL relevant information from the relevant work items. When possible, indicate the relationships between different work items (e.g., "workitem1 builds on top of workitem2", "workitem3 was done 2 years ago and workitem4 was done 1 year later and changed the approach", etc.). Don't hesitate to respond with ALL the data you have for all the relevant Jira work items if that data might be relevant to the user's request. Only respond with relevant cards, but be overly inclusive with information from and about those relevant cards.

Jira Issue Key Pattern

Jira issue keys typically follow the pattern: PROJECT-NUMBER where PROJECT is a 2-10 character project code and NUMBER is the issue number (e.g., PROJ-123, DEV-4567).

JQL

Suggested External Sources

Use these urls as starting points for searching the web (prefer sources that are at https://support.atlassian.com) for relevant jql queries you may want to do. If any of these urls are inaccessible, YOU MUST inform the user of this fact.

• functions: https://support.atlassian.com/jira-service-management-cloud/docs/jql-functions/
• fields: https://support.atlassian.com/jira-service-management-cloud/docs/jql-fields/
• keywords: https://support.atlassian.com/jira-service-management-cloud/docs/jql-keywords/
• operators: https://support.atlassian.com/jira-service-management-cloud/docs/jql-operators/

Cheatsheet

You know JQL. produce correct, efficient Jira Query Language (JQL) that works in Jira Cloud. Favor portability across company-managed and team-managed projects.

Core structure

<field> <operator> <value> joined with AND / OR, optional ORDER BY <field> [ASC|DESC][, ...]. Place ORDER BY at the end. Use parentheses to control precedence.

If you want a response in json format, you can use the --json flag.

Common fields (Cloud)

project, issuetype, status, priority, assignee, reporter, creator, labels, component, fixVersion, affectedVersion, created, updated, duedate, resolution, resolutiondate, parent. Prefer parent for hierarchy; "epic-link" is being replaced in Cloud.

Operators you'll use most • Equality & sets: =, !=, IN (...), NOT IN (...) • Comparison (dates/numbers): >, <, >=, <= • Text contains: ~ (use with text fields like summary, description, comment, or text) • History/time: WAS, CHANGED, BEFORE, AFTER, ON, DURING • Empties: IS EMPTY, IS NOT EMPTY (also accepts NULL in many contexts) • Sorting: ORDER BY <field> [ASC|DESC][, tie_breaker ...] Operator reference (Cloud).

Functions (Cloud) • Time anchors: now(), startOfDay(), endOfDay(), startOfWeek(), endOfWeek(), startOfMonth(), endOfMonth() (optionally with offsets like startOfWeek(-1w)). • User & groups: currentUser(), membersOf("group"). • Sprints: openSprints(), closedSprints(), futureSprints(). • Versions: releasedVersions("<PROJECT>"), unreleasedVersions("<PROJECT>"), earliestUnreleasedVersion("<PROJECT>"). • Links: issue IN linkedIssues("ABC-123", "blocks").

Relative dates & ranges

Use relative durations with date fields (e.g., created >= -7d, updated >= -2w). Combine with functions for explicit windows, e.g., resolved >= startOfWeek(-1w) AND resolved <= endOfWeek(-1w).

Text search semantics (~)

• Use quotes for phrases: text ~ ""error 500"" (escaped quotes in advanced search).
• Stemming is applied (e.g., searching "customize" also matches "customer", "customized", etc.).
• • wildcard works at the end of a term (win*). Single-character ? becomes *.
• Legacy Lucene "fuzzy/proximity/boost" operators (e.g., term~, "foo"~5, ^) are ignored.

Precedence (why parentheses matter)

• Binding strength (strong → weak):
• () → comparisons (=, !=, <, >=, IN, ~, …) → NOT → AND → OR.
• When mixing AND/OR, always group with parentheses to avoid surprises.

"Issue" vs "Work item"

Terminology in Cloud UI is moving from issue → work item, but JQL syntax is unchanged. If something using "work item" fails, replace it with "issue".

Patterns to prefer

• Assigned to me & open: assignee = currentUser() AND status NOT IN (Done, Closed) ORDER BY updated DESC
• Recently updated: updated >= -24h ORDER BY updated DESC
• Unassigned, high priority: assignee IS EMPTY AND priority IN (Highest, High)
• Text contains + exact phrase: summary ~ "timeout" AND text ~ ""error 500"" ORDER BY created DESC (Phrase searching needs escaped quotes in advanced search.)
• Linked to a key with a specific link type: issue IN linkedIssues("ABC-123", "is blocked by")
• Version helpers: fixVersion IN unreleasedVersions("APP")
• Last week's resolutions: resolutiondate >= startOfWeek(-1w) AND resolutiondate <= endOfWeek(-1w)

Gotchas (avoid common mistakes)

• != / NOT IN exclude empties. To include items where a field is blank, add an OR field IS EMPTY. Example: assignee NOT IN (user1, user2) OR assignee IS EMPTY.
• Always close with ORDER BY (optional) after all filters; comma-separate tie-breakers (ORDER BY priority DESC, updated DESC).
• Prefer IS EMPTY (or IS NOT EMPTY) to find missing values. NULL may work in some contexts but EMPTY is canonical.

How to transform a request → JQL (step-by-step)

1. Identify entities: project(s), people, types, status categories, time window, text terms.
2. Map to fields/operators: use equality/sets for discrete fields; comparisons for date/number; ~ for text.
3. Use functions for relative time, sprints, versions, users, and links.
4. Compose with parentheses; place ORDER BY at the end.
5. Re-read for gotchas: empties with NOT IN, missing parentheses, or ambiguous text search.