OpenClaw + Jira: Never Miss a Task Again

OpenClaw's Jira integration lets you create tickets, query sprint status, triage backlogs, and automate routine Jira work through an AI agent — without leaving your terminal. If you've ever lost a task because you didn't have time to file the ticket, or spent 20 minutes updating a sprint board after a standup, this integration is for you.

Here's how to configure it and what workflows become possible.

The Problem with Jira Workflows#

Jira is powerful and also time-consuming. Finding the right project, navigating to the right board, filling in the right fields, assigning to the right person — each individual ticket takes 3–5 minutes. Multiply that by the number of issues that come up in a day, and you've spent significant time on process overhead rather than actual work.

The other problem: tickets that never get created. You're deep in debugging, you notice a related issue, and you tell yourself you'll file it later. You don't. Three weeks later someone else hits the same bug.

OpenClaw solves both: capturing tasks is a one-sentence command, and routine Jira maintenance happens automatically.

Setup#

1. Install DenchClaw#

npx denchclaw

2. Configure Jira Credentials#

OpenClaw's Jira Skill uses the Jira REST API. You'll need:

• Your Jira instance URL (e.g., https://your-org.atlassian.net)
• Your email address
• An API token (generate at https://id.atlassian.com/manage-profile/security/api-tokens)

Set these as environment variables:

export JIRA_URL="https://your-org.atlassian.net"
export JIRA_USER="you@yourcompany.com"
export JIRA_TOKEN="your-api-token-here"

Or add them to your shell profile for persistence.

3. Load the Jira Skill#

In your OpenClaw session:

Load the Jira skill and help me manage tickets in the PAYMENTS project.

For full workspace configuration, see the DenchClaw setup guide.

Creating Tickets#

Instant Ticket Creation#

The most common workflow: capture a task or bug before you forget it.

Create a Jira bug in the PAYMENTS project:
Title: "Payment confirmation email delayed by up to 5 minutes"
Priority: Medium
Description: Users are reporting that order confirmation emails are 
arriving 3-5 minutes after payment, not immediately. 
Repro: Make a test purchase and check email timing.
Assign to the backend team.

The agent creates the ticket and returns the Jira issue key (e.g., PAYMENTS-1842). Total time: 15 seconds.

Ticket from a Conversation#

More naturally, you might describe an issue in plain language:

I just found that when a user's subscription expires mid-billing-cycle, 
the proration calculation is off by one day. Create a bug ticket for this.

The agent:

1. Extracts the key details (component: billing, type: bug, impact: financial)
2. Writes a clear description with reproduction steps
3. Suggests an appropriate priority (Medium-High given financial impact)
4. Creates the ticket

You spend 10 seconds describing the bug instead of 4 minutes filing it.

Bulk Ticket Creation#

After a sprint planning session or design review, you often have a list of tasks:

Create these tasks in the MOBILE project for the v3.2 sprint:
1. Update the onboarding flow to support new user types
2. Fix keyboard behavior on the address input screen (iOS only)
3. Add analytics events for the new checkout flow
4. Update app store screenshots for the new UI
All should be assigned to the mobile team and tagged with "v3.2"

The agent creates all four tickets, assigns them correctly, and adds the milestone tag. Four tickets in one command.

Querying and Searching#

Sprint Status#

What's the current sprint status for the BACKEND project?
How many tickets are in each state (To Do, In Progress, Done)?
Are there any blockers?

The agent queries the active sprint, counts by status, and flags any issues marked as blockers or that have been in-progress for more than a week without updates.

Your Personal Queue#

Show me all open Jira tickets assigned to me across all projects.
Sort by priority, then by due date.

Cross-project visibility in one query. Jira's own UI requires you to navigate project-by-project or set up saved filters.

Finding Duplicates#

I want to create a ticket about the payment webhook timeout issue.
Are there any existing tickets that might be the same problem?
Search for recent tickets about webhooks, timeouts, and payment processing.

The agent searches Jira before creating a new ticket, potentially saving you from creating a duplicate.

Stale Ticket Detection#

Which tickets in the BACKEND project have been "In Progress" 
for more than 10 days without any updates?

These are your stuck tickets — things that need a nudge, a reassignment, or a re-evaluation of scope.

Sprint Management#

Sprint Planning Prep#

The next sprint starts Monday. Pull all tickets labeled "sprint-candidate" 
in the BACKEND project, organized by story points. What's the total 
story point estimate?

The agent queries Jira, tallies story points, and gives you a capacity summary before the planning meeting.

End-of-Sprint Retrospective Data#

The current sprint ends today. Generate a summary:
- Total tickets committed vs. completed
- Average ticket age from creation to completion
- Which ticket types had the most slippage?
- Any tickets that were added mid-sprint?

This is data you'd normally export to a spreadsheet and calculate manually. The agent does it in under a minute.

Moving Tickets Between Sprints#

The following tickets aren't going to make it into this sprint.
Move them to the backlog: BACKEND-1201, BACKEND-1198, BACKEND-1187.
Add a comment to each explaining they were deferred.

Bulk operations that would take 10 minutes in the Jira UI take 30 seconds.

Automating Ticket Updates#

Closing Resolved Tickets#

I just merged PR #156 which fixes BACKEND-1142, BACKEND-1156, and BACKEND-1159.
Close all three tickets and add a comment linking to the PR.

The agent closes the tickets, adds the comment with the PR link, and moves them to "Done."

Status Updates from CI#

Configure a webhook or cron job to automatically update tickets when CI passes or fails:

# After a successful deploy
openclaw run "The v2.4.1 deploy to production succeeded. Update all tickets 
in the BACKEND-v2.4.1 sprint milestone to 'Released in v2.4.1' using the 
Fix Version field."

Daily Triage#

Run the morning triage for the SUPPORT project:
1. List all new tickets created yesterday that don't have a priority set
2. For each, read the description and suggest a priority
3. Assign any clearly security-related tickets to the security team
4. Flag anything that looks like a production incident

This runs automatically via cron every morning before your team's standup.

Storing Jira Data in DuckDB#

Sync Jira metadata to your local DuckDB workspace for richer analytics:

CREATE TABLE jira_issues (
  key VARCHAR PRIMARY KEY,
  project VARCHAR,
  type VARCHAR,
  summary VARCHAR,
  priority VARCHAR,
  status VARCHAR,
  assignee VARCHAR,
  created_at TIMESTAMP,
  updated_at TIMESTAMP,
  resolved_at TIMESTAMP,
  story_points FLOAT,
  sprint VARCHAR,
  labels VARCHAR[]
);

With this data locally, you can ask:

• "What's our average time from ticket creation to resolution this quarter?"
• "Which team member closes the most tickets per sprint?"
• "Are story point estimates improving over time (estimated vs. actual)?"

This is the kind of engineering analytics that normally requires a BI tool. With DuckDB and OpenClaw, it's a query away. Learn more about DenchClaw's workspace model.

Integration with Other Tools#

The Jira integration works alongside other Skills:

GitHub ↔ Jira: When a PR is merged, automatically close the linked Jira ticket. When a GitHub issue is filed, create the corresponding Jira ticket. See the OpenClaw GitHub integration.

Linear → Jira: For teams migrating from Linear to Jira (or vice versa), the agent can sync issues between the two. See the OpenClaw Linear integration.

Slack notifications: Post to Slack when high-priority tickets are created or when sprint goals are at risk.

FAQ#

Which Jira versions does OpenClaw support? The Jira Skill uses the Jira REST API v3, which is compatible with Jira Cloud and Jira Server 9+. Data Center deployments with API access also work.

Can OpenClaw update custom fields in Jira? Yes. Custom fields are accessible via the Jira API. You'll need to know the field ID (from your Jira admin settings). Tell the agent the field ID and it can read and write it.

Does OpenClaw have access to Jira permissions and audit logs? The agent uses your API token, which has the same permissions as your Jira user account. It doesn't have admin capabilities unless your account does.

Can OpenClaw create Jira epics and link stories to them? Yes. Epic creation and story linking use standard Jira API endpoints. The agent can create an epic and link multiple stories to it in one command.

Is there a risk of creating duplicate tickets? The agent can search for existing tickets before creating new ones if you ask it to. For automated workflows (e.g., creating a ticket from a CI failure), build a deduplication check into the instruction: "Check if there's already an open ticket about this before creating a new one."

Ready to try DenchClaw? Install in one command: npx denchclaw. Full setup guide →