jira-search_skill

This skill searches Jira issues using JQL, enabling filtered, paginated results and field selection for reports and lists.
  • JavaScript

3

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill 01000001-01001110/agent-jira-skills --skill jira-search

  • SKILL.md7.5 KB

Overview

This skill lets you search Jira Cloud issues using JQL queries, with support for filtering, pagination, field selection, and changelog expansion. It is implemented for cross-platform use (Node.js and Python scripts) and expects an authenticated Jira client. Use it to build reports, lists, and bulk operations from precise Jira query criteria.

How this skill works

The skill sends POST requests to the Jira /search endpoint with a JQL string, startAt, maxResults, fields, and optional expand parameters. It exposes a paginated search function and a helper that iterates pages to return all matching issues. Helper builders create common JQL clauses (project, status, assignee, date ranges) and a combine function to join conditions.

When to use it

  • Filter issues by project, status, assignee, label, or date range
  • Build dashboards, CSV exports, or automated reports from Jira data
  • Find unassigned, recent, or high-priority issues for triage
  • Prepare sets for bulk updates or scripted workflows
  • Retrieve changelogs or expanded fields for audit or migration tasks

Best practices

  • Always paginate for large result sets; use searchAllIssues helper to collect all pages
  • Request only the fields you need to reduce response size and latency
  • Quote values that contain spaces and use accountId (not email) for assignee filters
  • Escape special characters in free-text searches and prefer indexed fields for performance
  • Use expand=['changelog'] only when you need history to avoid heavy payloads

Example use cases

  • Get all open issues in project SCRUM for a sprint report
  • Export my issues created in the last 7 days for a weekly summary
  • Find unassigned bugs in a project to assign during triage
  • Collect issues with label "urgent" for an incident runbook
  • Retrieve issues updated in the last week with changelogs for audit

FAQ

It requires an authenticated Jira client (API token or OAuth) with access to the target project(s).

How do I avoid missing issues in large projects?

Use pagination. Set maxResults to a reasonable value (for example 100), and iterate startAt until you have retrieved total issues or use the provided searchAllIssues helper.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational