- Home
- Skills
- Grandcamel
- Jira Assistant Skills
- Jira Search
jira-search_skill
- Shell
4
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 grandcamel/jira-assistant-skills --skill jira-search- SKILL.md12.2 KB
Overview
This skill lets you find and act on JIRA issues using JQL (JIRA Query Language). It supports running queries, building and validating JQL, saving and sharing filters, exporting results to CSV/JSON, and performing controlled bulk updates. Designed for reporting, automation, and large-scale issue management.
How this skill works
You run JQL queries via a CLI that executes searches, paginates results, and returns selected fields. The skill can validate and build queries interactively, save filters on the server, export results with streaming for large datasets, and perform bulk updates with dry-run support. All actions require JIRA credentials set in environment variables and use the jira-as CLI wrapper.
When to use it
- Search issues by status, assignee, priority, labels, sprint, or custom fields
- Create saved filters for dashboards, monitoring, or team reporting
- Export issue lists to CSV/JSON for analysis or sharing
- Perform bulk updates (labels, priority, assignee) across many issues—use dry-run first
- Validate and build complex JQL before embedding in automation or scripts
- List available fields, functions, and suggestions when constructing queries
Best practices
- Always validate JQL before running large queries or bulk updates (--dry-run for bulk-update)
- Limit exported fields and use pagination or date splits for very large result sets
- Use saved filters for repeatable reports and toggle favourites to share with teams
- Use --max-results to avoid unexpected large returns and test with small scopes first
- Prefer streaming JSON/JSON Lines for very large exports to reduce memory pressure
Example use cases
- Find all open bugs assigned to the current user in the active sprint and export to CSV for status review
- Create a reusable filter for a team backlog and share it with the project group
- Bulk-add a label to hundreds of issues after triage, previewing changes with --dry-run before applying
- Build and validate a complex JQL from clauses, then save it as a filter for automated dashboards
- Export recent sprint metrics (key, summary, status, assignee) as JSON for analysis pipelines
FAQ
Set JIRA_SITE_URL, JIRA_EMAIL, and JIRA_API_TOKEN in your environment; the CLI uses these to authenticate.
How do I avoid accidental destructive changes?
Use --dry-run on bulk-update and filter delete to preview actions, and use --max-issues to limit scope during testing.