jira-jql

Write, debug, and optimize Jira Query Language statements.

40|6|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/magnus919/agent-skills --skill jira-jql
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-jql
Source: https://github.com/magnus919/agent-skills/tree/main/jira-jql
Command: npx skills add https://github.com/magnus919/agent-skills --skill jira-jql

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves the complexity of Jira's query language, enabling users to precisely filter, debug, and optimize issue searches without needing to memorize obscure syntax or function parameters.

Core Features & Use Cases

  • Expert Query Construction: Build complex filters using history operators like WAS and CHANGED, relative date offsets, and cross-project criteria.
  • Performance Optimization: Identify and resolve slow-running queries by applying best practices for indexed fields and efficient clause ordering.
  • Use Case: A project manager can use this skill to generate a query that identifies all high-priority bugs that were reopened in the last week across multiple product teams, ensuring no quality regressions are missed.

Quick Start

Ask the agent to write a JQL query that finds all unresolved bugs assigned to you that were updated in the last seven days.

Frequently Asked Questions about jira-jql

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

FAQPage Schema
How do I write a Jira JQL query to find unresolved bugs assigned to me that were updated recently?

To write a Jira JQL query for unresolved bugs assigned to you and updated recently, construct a statement combining status, assignee, and updated date operators. The skill guides you through building these precise cross-project search filters step by step.

What is the best way to track the historical state of a Jira issue using JQL?

Tracking the historical state of a Jira issue uses the WAS and CHANGED history operators in JQL. This enables complex search scenarios to identify previous statuses, assignees, or custom field values without manual changelog review.

Can I use relative date calculations in Jira JQL for agile reporting?

Yes, relative date calculations in Jira JQL support agile reporting by allowing dynamic time-based filters. You can generate queries using functions like startOfDay or endOfWeek to automatically adjust reporting windows for sprints and releases.

Why does my Jira JQL search run slowly and how can I optimize the filter performance?

Jira JQL searches run slowly due to unindexed fields or inefficient clause ordering. Optimize filter performance by applying best practices for indexed fields and restructuring query logic to minimize database load during complex searches.

Does JQL support complex search criteria across multiple Jira projects?

JQL supports complex search criteria across multiple Jira projects using cross-project filtering clauses. You can combine project keys with priority, status, and historical operators to isolate specific issues like reopened high-priority bugs.