Search and analyze Jira work
Write and refine JQL, inspect issues and links, identify stale or blocked work, summarize themes, and prepare reviewable reports.
Codex Skills for Jira help Codex search, create, update, organize, and summarize Jira work while respecting project configuration, permissions, workflow rules, and team conventions. Download the skills for issue triage, backlog refinement, sprint preparation, release tracking, automation, and reports through approved Jira APIs or connectors.
task: complete jira work management task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffUseful Jira work depends on project type, issue hierarchy, fields, screens, workflows, boards, sprints, versions, permissions, and the team's definition of ready and done.
These skills guide Codex to inspect the available Jira configuration and current issues before proposing queries, edits, transitions, automation, or summaries.
Write and refine JQL, inspect issues and links, identify stale or blocked work, summarize themes, and prepare reviewable reports.
Draft clear summaries, descriptions, acceptance criteria, reproduction steps, priorities, components, labels, links, and required fields.
Support backlog refinement, sprint preparation, epics, dependencies, versions, releases, transitions, and status reporting.
Design Jira automation rules and API workflows with explicit triggers, conditions, branches, permissions, safeguards, and audit expectations.
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
Identify Cloud or Data Center, site, project, issue types, fields, workflows, boards, permissions, conventions, and requested scope.
Search current issues, relationships, statuses, duplicates, required fields, active sprints, versions, and automation that may be affected.
Draft JQL, issue content, field updates, transitions, links, comments, or rules and show the intended records.
Use authorized access, limit bulk scope, confirm required fields and transitions, inspect results, and preserve an audit trail.
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Manage epics, stories, bugs, tasks, boards, sprints, versions, releases, development links, and engineering reports.
Organize requests, campaigns, operations, approvals, ownership, due dates, forms, and cross-team workflows.
Classify incoming issues, find duplicates, request missing evidence, assess impact, route ownership, and track resolution.
Create rules and API workflows for issue updates, notifications, synchronization, reporting, and controlled bulk operations.
Start with one defined outcome and provide the source material, constraints, and checks that matter.
These skills are designed for people who need dependable jira work management work with a visible process.
Refine backlogs, organize priorities, prepare sprints, track dependencies, and communicate progress.
Create actionable work, connect code and releases, triage defects, and keep status evidence current.
Manage ownership, workflows, due dates, approvals, requests, reporting, and cross-team coordination.
Review fields, workflows, permissions, automation, integrations, and governance before broad changes.
The skills require authorized Jira access for live actions. They must not bypass permissions, invent issue facts, transition work without approval, or apply broad changes without showing the exact scope first.
Install the complete skill folder and add the project-specific context before beginning.
Keep SKILL.md with issue, JQL, planning, workflow, automation, API, and reporting guidance.
Use project scope for team conventions and identifiers, or personal scope for reusable Jira practices.
Configure an approved Jira connector, MCP server, or API credential with the minimum permissions needed. Do not store tokens in the skill.
Provide site type, project keys, issue hierarchy, required fields, workflows, boards, sprint rules, definitions, and protected actions.
Practical answers about capabilities, limits, setup, and review.
Yes, when an approved Jira connection and suitable permissions are available. Proposed fields and scope should be reviewable.
Yes. They can write, explain, refine, and validate JQL against the available Jira environment.
They can support refinement, sprint preparation, issue movement, dependencies, and summaries within board rules and permissions.
Yes. They can design and review triggers, conditions, branches, actions, smart values, permissions, loops, and failure handling.
The workflow can adapt to Cloud or Data Center, but API routes, authentication, features, and configuration must match the stated deployment.
Clear context. Purposeful work. Relevant checks. A result others can understand.