jira-jql-patterns

Construct JQL query patterns to filter Jira issues via jira-cli.

9|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/yebot/rad-cc-plugins --skill jira-jql-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-jql-patterns
Source: https://github.com/yebot/rad-cc-plugins/tree/main/plugins/jira-cli/skills/jira-jql-patterns
Command: npx skills add https://github.com/yebot/rad-cc-plugins --skill jira-jql-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jira-cli.

What problem does it solve?

Constructing effective JQL (Jira Query Language) queries for advanced issue filtering and reporting can be complex and time-consuming. This skill provides a comprehensive guide to JQL patterns, enabling you to quickly build powerful queries and extract the exact information you need from Jira.

Core Features & Use Cases

  • Essential Field & Operator Reference: Get quick access to common issue, people, date, and agile fields, along with equality, comparison, and text search operators for precise filtering.
  • Powerful JQL Functions: Learn to leverage built-in functions for users, dates, and sprints to create dynamic and context-aware queries.
  • Common Query Patterns: Access ready-to-use JQL templates for finding your current work, recently completed tasks, priority issues, and time-based queries, streamlining your reporting.

Quick Start

To find all issues assigned to you that are not yet "Done" or "Closed", ask the skill to "Show me the JQL query to list all issues assigned to the current user that are still in progress."

Frequently Asked Questions about jira-jql-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write JQL queries to filter Jira issues by status and assignee?

JQL queries filter Jira issues using field operators and values. Use `assignee = currentUser()` and `status != Done` to find your open work, or combine multiple conditions with AND/OR to narrow results by project, priority, labels, and other fields. The skill provides ready-made patterns for common scenarios.

What JQL operators and functions are available for advanced issue searching?

JQL supports equality operators (=, !=, IN), comparison operators (>, >=, <, <=), text search (~, !~), and temporal functions like `startOfDay()`, `startOfWeek()`, and `openSprints()`. Historical operators WAS and CHANGED track field changes. These combine to enable dynamic, context-aware queries without manual updates.

Can I use JQL to find overdue issues or tasks in my current sprint?

Yes. JQL includes date fields (created, updated, duedate, resolved) and sprint functions (openSprints(), closedSprints()) to target time-based queries. Use `duedate < startOfDay()` to find overdue items, or `sprint = openSprints()` and `status != Done` to isolate current sprint work.

How do I construct JQL patterns for reporting on bugs, stories, and epics?

JQL filters by issue type, labels, components, and Epic Link fields. Use `type = Bug AND status != Closed` for bug reports, `type = Story AND assignee = currentUser()` for story tracking, or `"Epic Link" = PROJ-123` to list all issues in an epic.

Does JQL work with jira-cli for automated issue extraction and reporting?

Yes. This skill builds JQL patterns specifically for jira-cli, enabling you to extract issues programmatically across all standard fields—project, key, summary, priority, assignee, and more—and automate filtering, reporting, and backlog prioritization workflows.

What are the limits of JQL when filtering across multiple projects or custom fields?

JQL handles multi-project queries and supports standard issue fields out of the box. Custom fields and Jira Cloud vs. Server syntax may differ; this skill covers core fields and operators. Complex nested conditions or very large result sets may require pagination or result limits depending on your Jira instance.