Originally published on Remote OpenClaw.
Marketplace
Free skills and AI personas for OpenClaw — browse the marketplace.
Join the Community
Join 1k+ OpenClaw operators sharing deployment guides, security configs, and workflow automations.
Why Connect OpenClaw to Jira?
Jira is the standard for issue tracking in software development teams, used by over 75,000 organizations worldwide. The OpenClaw-Jira integration brings AI automation to your existing Jira workflows without requiring your team to learn a new tool or change their processes.
Based on hands-on testing with engineering teams running Scrum and Kanban boards, the integration shines in three areas: automated issue triage (classifying and routing incoming bugs and feature requests), sprint health monitoring (flagging at-risk stories and suggesting scope adjustments), and standup report generation (summarizing yesterday's progress and today's plan from Jira data).
For teams already invested in the Atlassian ecosystem, this integration is particularly powerful when combined with Confluence for documentation and Bitbucket for code reviews. If you are new to OpenClaw, start with the beginner setup guide.
Prerequisites
- OpenClaw installed and running — local or hosted deployment.
- Jira Cloud or Data Center instance — with admin access to create API tokens.
- Atlassian API token (Cloud) or Personal Access Token (Data Center).
- Project key — the short identifier for your Jira project (e.g., "PROJ").
- Node.js 18+ — for the OpenClaw Jira skill runtime.
Step-by-Step Setup
Step 1: Generate an Atlassian API Token
For Jira Cloud, create an API token at id.atlassian.com:
# Store your Jira credentials
export JIRA_DOMAIN="your-domain.atlassian.net"
export JIRA_EMAIL="your-email@company.com"
export JIRA_API_TOKEN="your_api_token_here"
# Verify the connection
curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
"https://$JIRA_DOMAIN/rest/api/3/myself" | jq '.displayName'
For Jira Data Center, generate a Personal Access Token from your profile settings:
# Data Center configuration
export JIRA_BASE_URL="https://jira.yourcompany.com"
export JIRA_PAT="your_personal_access_token"
# Verify
curl -s -H "Authorization: Bearer $JIRA_PAT" \
"$JIRA_BASE_URL/rest/api/2/myself" | jq '.displayName'
Step 2: Configure OpenClaw
# ~/.openclaw/config.yaml
integrations:
jira:
type: cloud # or "datacenter"
domain: ${JIRA_DOMAIN}
email: ${JIRA_EMAIL}
api_token: ${JIRA_API_TOKEN}
default_project: "PROJ"
issue_types:
- Bug
- Story
- Task
- Epic
skills:
- name: jira-manager
trigger: "jira"
actions:
- create_issue
- update_issue
- transition_issue
- search_jql
- manage_sprint
- generate_report
Step 3: Install and Verify
# Install the Jira skill
openclaw skill install jira-manager
# Test issue creation
openclaw run "Create a Jira Bug in project PROJ titled 'Login page returns 500 error' with priority High and label 'production'"
# Test JQL search
openclaw run "Search Jira for all open bugs in PROJ assigned to me, sorted by priority"
Example Use Cases
1. Automated Bug Triage
OpenClaw can analyze incoming bug reports, set priority based on severity keywords, assign to the right developer based on component ownership, and add relevant labels:
openclaw run "Triage this bug report and create a Jira issue: 'Users in the EU region are experiencing 30-second load times on the dashboard. Affects approximately 2,000 users. Started after yesterday's deployment.'"
2. Sprint Retrospective Reports
openclaw run "Generate a sprint retrospective report for PROJ Sprint 23: velocity achieved vs planned, stories completed, stories carried over, bugs found during sprint, and team capacity utilization"
3. Cross-Project Dependency Tracking
For organizations with multiple Jira projects, OpenClaw can identify and flag cross-project dependencies, helping project managers avoid bottlenecks:
openclaw run "Scan all active sprints across projects PROJ, PLATFORM, and INFRA — identify any blocked issues and their blocking dependencies"
Marketplace
Free skills and AI personas for OpenClaw — browse the marketplace.
Troubleshooting Tips
403 Forbidden Errors
This usually means your API token account lacks the required project permissions. Verify the account has "Browse Projects," "Create Issues," and "Edit Issues" permissions in the project's permission scheme.
JQL Syntax Errors
OpenClaw translates natural language to JQL, but complex queries may produce invalid syntax. If a search fails, try simplifying the request or providing the JQL directly:
openclaw run "Run this Jira JQL query: project = PROJ AND status = 'In Progress' AND assignee = currentUser() ORDER BY priority DESC"
Workflow Transition Failures
If an issue cannot be transitioned, it likely means a required field is missing or a workflow condition is not met. Check your Jira workflow configuration for required fields on the target transition.
Slow API Responses
Jira Cloud API responses can be slow for large projects (10,000+ issues). Use specific JQL filters to narrow results rather than querying entire projects.
Limitations and Known Issues
- Jira Service Management: The integration works with Jira Software but has limited support for Jira Service Management request types and SLA fields.
- Attachments: File uploads through the API are limited to 10MB per attachment on Jira Cloud Free and Standard plans.
- Advanced Roadmaps: Jira Premium's Advanced Roadmaps (Plans) are not accessible through the standard REST API. OpenClaw cannot modify roadmap data directly.
- Permissions complexity: Jira's permission schemes can be intricate. In some configurations, even accounts with apparent admin access may lack specific API permissions. Test thoroughly.
For the official Jira API documentation, see developer.atlassian.com.
If you are evaluating alternatives, compare this with the Linear integration which offers a simpler API for smaller teams.
Frequently Asked Questions
Does OpenClaw work with both Jira Cloud and Jira Data Center?
Yes. OpenClaw supports both Jira Cloud (using API tokens) and Jira Data Center (using personal access tokens or OAuth). The configuration differs slightly — Cloud uses your Atlassian domain while Data Center uses your self-hosted URL.
Can OpenClaw auto-assign Jira issues based on content?
Yes. OpenClaw can analyze issue descriptions and automatically assign them to the appropriate team member based on expertise matching, current workload, and historical assignment patterns. This requires configuring a team roster in your OpenClaw config.
How does OpenClaw handle Jira workflow transitions?
OpenClaw respects your Jira workflow rules and transitions. It can move issues through valid transitions (e.g., To Do, In Progress, Done) but cannot bypass required fields or conditions set in your workflow configuration.
What Jira permissions does OpenClaw need?
OpenClaw needs a Jira account with permissions to create issues, edit issues, transition issues, and read project data. For sprint management, the account also needs Scrum board admin permissions. We recommend creating a dedicated service account.
Top comments (0)