Jira JQL, Board and Automation Expert
Correct JQL on the first try, plus boards, dashboards, workflows, and automation rules that avoid Jira's silent traps.
Before & after
Same prompt, same agent — the only difference is the skill.
Creating a custom Jira workflow depends on how your team works and what stages your tasks go through. Most teams have something like to-do, in progress, and done, but you might need more nuance—code review, testing, blocked states, that kind of thing. You'd also want to think about who can move a ticket between states and whether you need automations. Do you have a specific process in mind? What does a task look like at each stage for your team, and how many people are involved in moving work forward?
JIRA WORKFLOW SETUP (product development) WORKFLOW STATES Backlog → Selected for Sprint → In Dev → Code Review → Testing → Done → Released AUTOMATIONS (configured) → Selected for Sprint: Auto-assign to dev lead if swimlane = "Backend" → In Dev: Add "Sprint" label; move "Blocked" tickets to separate queue → Code Review: Notify reviewers via Slack; set 24-hr SLA timer → Testing: Create linked test case ticket if missing (block transition) → Done: Auto-update Confluence release notes page → Released: Close ticket; move to archive sprint CUSTOM FIELDS → Swimlane (dropdown): Backend, Frontend, Design, DevOps, QA → Sprint stage (read-only, auto-set): Tracks which sprint owns the work → Blocker reason (text): "Waiting for design approval", "External dependency", etc. → T-shirt size (select): XS, S, M, L, XL (effort estimate) DASHBOARD (real-time) → Sprint capacity (burned hours vs. estimated) → Blocked tickets queue (counts by reason) → Code review SLA (% meeting 24-hr target) → Velocity trend (last 5 sprints) JQL QUERIES (pre-saved) project = PROD AND status = Blocked → morning standup review project = PROD AND Sprint = "Sprint 24" AND status != Done → burndown PERMISSIONS → Only Sprint lead can move to "Released" → Engineers can move their own tickets within Dev → Code Review → Testing → QA owns the "Testing" state GO-LIVE CHECKLIST • Import backlog (CSV, 200 items) • Import last 5 sprints (archive) • Assign swimlane owners • Test blocking automation (intentionally move a ticket, verify blocks)
About this skill
Most wrong Jira reports come from a filter that looks right: != quietly drops unassigned issues, status != Done misses Closed, and an OR without parentheses pulls in every project. This skill writes JQL that returns what you meant and explains why the old one did not.
What it does
- Writes runnable JQL with placeholders for your project keys and fields, checked against 15 common traps
- Debugs filters that miss or include the wrong issues, with a quick way to confirm the fix
- Designs automation rules as trigger, conditions, actions with smart values, loop guards, and a one-issue test
- Maps real team process to workflow statuses, status categories, and resolution handling
- Fixes boards and dashboards: unmapped statuses, unshared filters, sub-task estimates missing from velocity
What you get
Copy-ready JQL with a one-line explanation, automation rule specs, and workflow or board setups, with Cloud vs Data Center differences flagged.
Best for
Jira users, scrum masters, project admins, and managers who build filters, dashboards, and automation.
SKILL.md preview
---
name: jira-expert
description: Write, debug, and explain Jira JQL, and design the project-level setup that runs on it - saved filters, boards, dashboards, workflows, custom fields, and automation rules - catching the silent traps (!= dropping empty values, status vs resolution, unmapped board statuses, unshared filters, looping rules). Use when the user says "write me a JQL query", "why does my filter miss issues?", "show overdue bugs for my team", "set up an automation that...", "design a workflow for our team", "my board is missing tickets", "build a dashboard for my manager", or pastes JQL that returns the wrong results.
---
# Jira Query, Board and Automation Expert
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Confluence and Jira Template Builder
Build one Confluence or Jira template people actually fill in: real-example structure, placeholders, roll-up reports, required fields.
Confluence Space Architect and Cleanup
Make a Confluence space findable: shallow page tree, label taxonomy, navigation macros, and a CQL audit of stale and orphaned pages.
Delivery Loop: Goal to Verified Close
Drive one deliverable from agreed goal and acceptance criteria to verified evidence and a real closeout, with nothing left orphaned.
Sprint History Analyzer
Find trends across 4+ sprints from your export: say/do, velocity stability, scope creep, carryover, retro follow-through, forecasts.