Jira

The Fastest Way: HeraClaw Cloud ⚡

Skip the Atlassian Marketplace approval, OAuth configuration, and webhook setup. HeraClaw Cloud comes with Jira integration pre-configured and ready to use in 60 seconds.

Why HeraClaw Cloud for Jira?

✅ Ready in 60 seconds - No Atlassian app registration, no OAuth 2.0 setup, no marketplace approval wait ✅ No marketplace approval needed - Bypass the weeks-long Atlassian approval process ✅ Pre-configured connection - Works immediately after workspace authorization ✅ Always updated - We handle Jira API changes and deprecations automatically ✅ Professional support - If anything breaks, we fix it for you ✅ Secure by default - Enterprise-grade security, SOC 2 compliant infrastructure ✅ Zero maintenance - No webhook management, no SSL certificates, no uptime monitoring

How it works:

1. Sign up at cloud.getopenclaw.ai (takes 60 seconds)
2. Go to Integrations → Jira
3. Click 'Connect to Jira'
4. Authorize our app for your Jira instance
5. Done! Start managing projects with AI assistance

Get Started: Start with HeraClaw Cloud →

Complete Guide to OpenClaw + Jira

Jira is where enterprise teams plan, track, and ship software. With over 65,000 companies worldwide using it for project management, issue tracking, and agile workflows, Jira is the backbone of modern software development and team collaboration.

OpenClaw's Jira integration brings powerful AI assistance directly into your project management workflow, eliminating context-switching and making sprint planning, issue triage, and roadmap management dramatically faster.

Whether you're running a 5-person startup or a 5,000-employee enterprise, this integration transforms how your team manages work. No manual JQL queries to write, no dashboard switching - just ask your AI assistant and get instant, intelligent project insights.

Why Use Jira with OpenClaw?

Jira's rich API and enterprise architecture make it one of the most powerful platforms for AI-enhanced project management. Here's why the OpenClaw + Jira combination is transformative:

1. Enterprise-Grade Project Visibility

Jira's permission system was built for enterprise complexity, and OpenClaw leverages it completely:

• Project-level control: Restrict access to specific projects (Engineering, Product, Marketing)
• Role-based permissions: Only users with certain roles (Admins, Project Leads, Developers) can query data
• Board-specific access: Different teams see different boards and backlogs
• Issue-level security: Respect Jira's security schemes and permission levels
• Multi-site support: Different configs per Jira site for multi-tenant organizations
• Audit trails: Track every query and action for compliance review

This makes it perfect for enterprises where security and data isolation are critical. Your security team can review exactly who queried what data, when.

2. Natural Language JQL - No Syntax Required

Forget memorizing JQL syntax. Just ask in plain English:

"Show me all P0 bugs assigned to me""What tasks are blocking the Q2 launch?""List overdue issues in the Mobile project""Find all stories in the current sprint without story points""Show me issues created this week with no assignee"

The assistant translates your natural language into proper JQL queries, executes them, and formats the results beautifully. Your team can query Jira without learning JQL.

3. Sprint Planning Made Effortless

Jira's sprint management pairs perfectly with AI assistance:

• Sprint capacity analysis: "Do we have capacity for issue MOBILE-123 this sprint?"
• Velocity tracking: "What's our team velocity over the last 4 sprints?"
• Sprint health checks: "What issues are at risk of missing the sprint?"
• Story point estimation: "Suggest story points for these 5 issues based on similar past work"
• Sprint summaries: "Summarize what we accomplished in Sprint 47"
• Dependency detection: "What issues depend on CORE-456?"

Example: During sprint planning, the product owner asks "What's our average velocity?" The assistant queries the last 5 sprints, calculates the average (38 points), and recommends committing to 35-40 points for the upcoming sprint.

4. Rich Formatting for Project Data

Jira data is complex - the assistant makes it readable:

• Structured issue summaries: Issue key, title, status, assignee, priority at a glance
• Board visualizations: Text-based kanban views showing column distribution
• Burndown insights: "We're tracking 15% behind, recommend moving 3 issues to next sprint"
• Timeline summaries: Roadmap milestones with completion percentages
• Custom field display: CFO approval status, legal review, customer urgency - all formatted clearly
• Comment threading: Full comment history with timestamps and authors

Technical project data looks professional and is easy to scan. No more squinting at dense Jira screens.

5. Automated Issue Creation and Updates

Create and modify issues via natural language:

• Issue creation: "Create a bug: Login fails on iOS 17, assign to Sarah, priority P1"
• Bulk updates: "Move all 'Ready for QA' issues to 'In QA' and assign to the QA team"
• Status transitions: "Move BACKEND-789 to Done and add comment 'Deployed to production'"
• Field updates: "Set the fix version for all P0 bugs to 2.1.0"
• Watchers and notifications: "Add me as a watcher to all issues in Epic PLATFORM-100"

No form-filling, no clicking through Jira's UI. Just describe what you want, and it happens.

6. Cross-Project Intelligence

For organizations with multiple Jira projects:

• Cross-project queries: "Show all P0 issues across Engineering, Mobile, and Backend projects"
• Resource allocation: "Which developers are overloaded across all projects?"
• Dependency tracking: "What Backend issues is the Mobile team waiting on?"
• Portfolio planning: "What's the overall progress on the Q2 OKRs across all teams?"
• Shared component tracking: "All issues affecting the Auth Service across projects"

Perfect for program managers who need visibility across multiple teams and projects.

7. Integration with Atlassian Ecosystem

OpenClaw connects to your entire Atlassian stack:

• Confluence: "Pull requirements from the Mobile Redesign spec in Confluence"
• Bitbucket: "Show me PRs linked to BACKEND-456"
• Jira Service Management: "Create an incident ticket from this P0 bug"
• Jira Align: "What initiatives are these epics mapped to?"

Your entire Atlassian workflow becomes AI-accessible.

8. Advanced Automation and Workflows

Leverage Jira's automation with AI intelligence:

• Smart assignment: "Assign new security bugs to whoever fixed the most security issues last quarter"
• SLA monitoring: "Alert me if any customer-facing bugs are approaching SLA breach"
• Release automation: "When Epic MOBILE-200 is done, create a release candidate in Jira"
• Escalation workflows: "If a P0 bug is unassigned for 30 minutes, notify the on-call engineer"

Real-World Use Cases

1. Engineering Manager: Sprint Planning and Velocity Tracking

Scenario: You're an engineering manager leading a team of 8 developers. Every two weeks you run sprint planning, and you need to:

• Understand team capacity
• Review past velocity
• Identify blockers
• Commit to a realistic sprint goal

Manually, this involves opening 5+ Jira dashboards, exporting velocity charts, checking individual workloads, and cross-referencing dependencies.

How OpenClaw helps:

During sprint planning meeting:

• Velocity check: "What's our average velocity over the last 4 sprints?" → "38 story points (range: 32-44)"
• Capacity analysis: "Who has capacity this sprint?" → "Sarah: 8 points available, Mike: 13 points, team total: 42 points"
• Backlog refinement: "Show top 10 backlog items sorted by priority" → Formatted list with story points and dependencies
• Sprint health: "Are we on track for the Q2 launch epic?" → "Yes, 67% complete, 8 issues remaining, projected completion Sprint 49"
• Blocker identification: "What issues are blocked?" → "3 issues blocked: BACKEND-123 (waiting on API design), MOBILE-456 (waiting on backend), INFRA-789 (waiting on AWS approval)"

Impact:

• Sprint planning meetings cut from 2 hours to 45 minutes
• More accurate sprint commitments (85% → 95% sprint completion rate)
• Team morale improves (fewer failed sprints)
• Engineering director gets instant sprint health updates without asking you

2. Product Manager: Roadmap Management and Stakeholder Updates

Scenario: You're a product manager managing a roadmap with 15 epics across 3 quarters. You need to:

• Track epic progress
• Identify at-risk features
• Provide weekly stakeholder updates
• Prioritize incoming requests

Manually, you spend 4-6 hours per week updating spreadsheets, checking Jira, and drafting status emails.

How OpenClaw helps:

• Weekly status: "Generate executive summary of Q2 roadmap progress" → Professional summary with completion percentages, at-risk items, and blockers
• Epic health: "Which epics are behind schedule?" → "Mobile Redesign (Epic-45): 15% behind, recommend descoping 3 stories; Payment Integration (Epic-67): on track"
• Feature requests: "Create a story for dark mode in the Mobile project, link to Epic-45, priority Medium" → Issue created and linked in 2 seconds
• Stakeholder queries: CEO asks "When will the new analytics dashboard launch?" → "Epic-78 is 73% complete, projected completion April 28, on track for Q2 target"
• Dependency mapping: "What features depend on the new API?" → List of 12 issues with assignees and timelines

Impact:

• Stakeholder update prep time: 4 hours → 20 minutes per week
• Roadmap visibility increases (executives can self-serve status)
• Faster response to "when will X ship?" questions (instant vs 30-minute Jira diving)
• More time for actual product work instead of status reporting

3. DevOps Engineer: Incident Management and Postmortem Automation

Scenario: You're on-call for production systems. When incidents happen, you need to:

• Create incident tickets
• Track resolution progress
• Link related issues
• Generate postmortems
• Track action items

During a 2am outage, every second counts. Manually creating tickets, updating status, and documenting the incident adds 15-20 minutes of overhead.

How OpenClaw helps:

When PagerDuty alerts fire:

• Instant incident creation: "Create P0 incident: API latency spike, service degraded, assign to me" → Issue INCIDENT-234 created in 2 seconds
• Status updates: "Add comment to INCIDENT-234: Identified root cause, database connection pool exhausted" → Comment added with timestamp
• Related issues: "Find all issues related to database performance in the last 30 days" → 7 related issues found, potential pattern identified
• Team notification: "Add watchers: backend-team, engineering-director to INCIDENT-234" → Team notified automatically
• Resolution tracking: "Move INCIDENT-234 to Resolved, add resolution: Increased connection pool size, deployed fix v2.3.1"
• Postmortem creation: "Generate postmortem for INCIDENT-234" → Full postmortem template with timeline, impact, root cause, action items

Impact:

• Incident response time: 45 min → 28 min average (37% faster)
• Better documentation (100% of incidents have complete postmortems vs 60% before)
• Pattern detection (AI identifies recurring issues automatically)
• Action item tracking (all postmortem actions auto-created as Jira issues)

4. Support Team Lead: Bug Triage and Customer Escalation

Scenario: You lead a customer support team. Customers report bugs via Zendesk, and you need to:

• Triage bugs (P0/P1/P2)
• Create Jira issues for engineering
• Track fix status
• Notify customers when fixed
• Identify bug trends

Manually, support agents spend 30% of their time creating Jira issues, checking status, and updating customers.

How OpenClaw helps:

• Bug creation from tickets: "Create bug from Zendesk #12345: Payment fails for EU customers using AmEx, priority P1, assign to payments-team" → Issue created with Zendesk link
• Status checks: Customer asks "When will my bug be fixed?" → "Check SUPPORT-789 status" → "In QA, targeted for release 2.1.0 on April 15"
• Bulk triage: "Show all untriaged bugs from this week" → 23 bugs listed, sorted by customer impact
• Trend analysis: "What are the top 5 bug categories this month?" → "1) Payment issues (12), 2) Login failures (8), 3) Mobile crashes (7), 4) Email notifications (5), 5) Performance (4)"
• Customer impact: "How many customers are affected by the login bug?" → "47 customers, including 3 enterprise accounts (Acme Corp, TechCo, BigBank)"

Impact:

• Bug triage time: 2 hours/day → 30 min/day (75% reduction)
• Customer satisfaction increases (faster status updates)
• Engineering gets better bug reports (AI prompts for reproduction steps)
• Support team morale improves (less manual Jira data entry)

5. QA Lead: Test Case Management and Release Validation

Scenario: You're the QA lead preparing for a major release. You need to:

• Track test coverage
• Identify untested features
• Validate release readiness
• Create test plans
• Report on quality metrics

Manually, this involves spreadsheets, Jira filters, TestRail integration, and manual status checks across 100+ issues.

How OpenClaw helps:

• Test coverage: "What issues in Release 2.1.0 don't have QA approval?" → 8 issues listed, assigned to QA team
• Regression planning: "Create test plan for Release 2.1.0 based on changed components" → Test plan with 34 test cases auto-generated
• Bug severity analysis: "Show all P0 and P1 bugs in Release 2.1.0" → 2 P0 (both fixed), 5 P1 (3 fixed, 2 in QA)
• Release readiness: "Is Release 2.1.0 ready to ship?" → "Not ready: 2 P1 bugs still in QA, 8 issues without QA approval, recommend 2-day delay"
• Quality metrics: "What's our bug escape rate for the last 3 releases?" → "4.2% (industry avg: 8%), improving trend"

Impact:

• Release validation time: 4 hours → 45 minutes (81% reduction)
• Fewer production bugs (better test coverage identification)
• Release confidence increases (data-driven go/no-go decisions)
• QA team can focus on testing instead of status tracking

6. Scrum Master: Daily Standup Preparation and Blocker Identification

Scenario: You're a Scrum Master facilitating daily standups for 3 teams (24 developers). Before each standup, you need to:

• Review sprint progress
• Identify blockers
• Check if anyone is overloaded
• Prepare discussion topics

Manually, this requires checking 3 sprint boards, reviewing 50+ issues, and identifying patterns - taking 30-45 minutes each morning.

How OpenClaw helps:

Each morning at 8:30am (automated):

• Sprint progress: "What's the burndown status for Team Alpha, Beta, and Gamma?" → "Alpha: on track (18/40 pts done), Beta: ahead (25/35 pts done), Gamma: at risk (8/42 pts done, recommend review)"
• Blocker report: "What issues are blocked across all teams?" → 5 issues listed with blocker reasons and owners
• Workload check: "Who has the most open issues?" → "Mike: 8 issues (recommend redistribution), Sarah: 2 issues (capacity available)"
• Discussion topics: "What issues had the most activity yesterday?" → "BACKEND-456: 12 comments, API design debate; MOBILE-789: status changed 3 times, potential thrashing"
• Standup summary: "Generate standup talking points" → Formatted summary with progress, blockers, and discussion items

Impact:

• Standup prep time: 45 min → 5 min per day (89% reduction)
• Standup meetings more focused (15 min → 10 min average)
• Blockers resolved faster (identified proactively vs reactively)
• Teams feel supported (Scrum Master always prepared with context)

7. Engineering VP: Cross-Team Visibility and Resource Allocation

Scenario: You're the VP of Engineering overseeing 5 teams (50 engineers) working on 12 projects. You need:

• Executive-level visibility across all teams
• Resource allocation insights
• Risk identification
• Board-level reporting

Manually, you rely on weekly status reports from managers, which are often outdated and incomplete.

How OpenClaw helps:

• Executive dashboard: "Give me a summary of all active projects" → 12 projects with health status (8 green, 3 yellow, 1 red), completion percentages, and next milestones
• Resource analysis: "Which teams are overallocated?" → "Mobile team: 115% allocated (2 engineers needed), Backend team: 87% (capacity available)"
• Risk assessment: "What projects are at risk of missing Q2 deadlines?" → "Payment Modernization (45% complete, needs 65% by end of month), recommend adding 2 engineers or descoping"
• Investment tracking: "How are we allocating engineering time across product vs infrastructure vs tech debt?" → "Product: 62%, Infrastructure: 23%, Tech debt: 15% (recommend increasing tech debt to 20%)"
• Board prep: "Generate executive summary for board meeting" → Professional report with velocity trends, delivery metrics, and strategic initiatives progress

Impact:

• Executive visibility: weekly → real-time
• Board prep time: 6 hours → 1 hour
• Better resource allocation decisions (data-driven vs gut-feel)
• Earlier risk detection (identify problems weeks earlier)

8. Release Manager: Release Planning and Coordination

Scenario: You're coordinating a major release involving 4 teams, 80+ issues, and dependencies across Backend, Mobile, and Infrastructure. You need to:

• Track release progress
• Manage dependencies
• Coordinate deployment timing
• Communicate with stakeholders

Manually, this involves daily status meetings, spreadsheet tracking, and constant Jira dashboard checking.

How OpenClaw helps:

• Release status: "What's the status of Release 2.0?" → "78% complete (62/80 issues done), 18 in progress, on track for April 30 release"
• Dependency tracking: "What issues must be completed before we can release?" → "Critical path: 5 issues (BACKEND-123, MOBILE-456, INFRA-789, BACKEND-234, MOBILE-567), all currently in progress"
• Team coordination: "Which teams are behind schedule?" → "Mobile team: 2 issues behind (recommend pairing with backend engineers), other teams on track"
• Risk analysis: "What could delay the release?" → "INFRA-789 (database migration) is complex, recommend dry-run this week; MOBILE-567 waiting on App Store approval (7-day lead time)"
• Stakeholder updates: "Generate release status email" → Professional update with progress, risks, and next steps

Impact:

• Release coordination time: 10 hours/week → 3 hours/week
• Fewer last-minute surprises (proactive risk identification)
• Better cross-team coordination (dependency visibility)
• On-time releases improve from 60% → 85%

Features Deep Dive

Natural Language JQL

Query Jira without learning JQL syntax:

• "Show me all bugs" → project = BACKEND AND type = Bug
• "High priority issues assigned to me" → assignee = currentUser() AND priority = High
• "Overdue tasks in the Mobile project" → project = MOBILE AND due < now() AND resolution = Unresolved
• "Stories without story points" → type = Story AND "Story Points" is EMPTY
• Complex queries: "Show P0 bugs created this week in Backend or Mobile projects assigned to the API team" → Proper JQL with multiple conditions

Issue Creation and Updates

Create and modify issues via natural language:

• Create: "Create a bug: Login button doesn't work on Safari, assign to frontend-team, priority High"
• Update: "Change BACKEND-456 priority to Critical and add label 'customer-facing'"
• Bulk operations: "Add label 'Q2-release' to all issues in Epic-100"
• Status transitions: "Move all 'In Review' issues to 'Done' if they have QA approval"
• Comments: "Add comment to MOBILE-789: Waiting on API deployment before testing"

Sprint Management

Complete sprint lifecycle support:

• Sprint creation: "Create Sprint 48 starting April 15, ending April 28"
• Sprint planning: "What's our velocity?" "Do we have capacity for these 5 issues?"
• Sprint updates: "Add BACKEND-456 to current sprint"
• Sprint reports: "Generate sprint retrospective for Sprint 47"
• Velocity tracking: "Show velocity trend for the last 6 sprints"

Epic and Roadmap Management

Manage long-term planning:

• Epic creation: "Create epic: Mobile App Redesign, target Q2 2026"
• Epic progress: "What's the completion percentage of Epic-45?" → "67% (12/18 issues done)"
• Roadmap queries: "Show all Q2 epics with their status"
• Epic dependencies: "What epics depend on the API Modernization epic?"
• Epic summaries: "Summarize progress on Epic-100 for stakeholders"

Advanced Filters and Views

Saved filters and custom queries:

• My work: "Show my open issues"
• Team dashboards: "Show the Mobile team's current sprint board"
• Custom views: "Show all customer-facing bugs sorted by customer count"
• Recently updated: "What issues were updated in the last 24 hours?"
• Watching: "Show issues I'm watching"

Custom Fields Support

Query and update custom fields:

• "Show issues where Customer Impact is High"
• "Set Legal Approval to Approved for BACKEND-456"
• "List all issues with Security Review = Pending"
• Custom field types: text, select, multi-select, date, number, user picker

Workflow Automation

Automate common workflows:

• Auto-assignment: "Assign new security bugs to the security team"
• Status automation: "When a PR is merged, move the issue to QA"
• Escalation: "If a P0 bug is unassigned for 1 hour, notify the engineering manager"
• SLA monitoring: "Alert if customer issues approach SLA breach"

Reporting and Analytics

Generate insights from Jira data:

• Velocity reports: "Show team velocity for Q1 2026"
• Burndown charts: "What's our sprint burndown status?"
• Bug trends: "Show bug creation vs resolution rate for last 3 months"
• Cycle time: "What's our average time from 'In Progress' to 'Done'?"
• Team performance: "Which team has the highest story point completion rate?"

Multi-Project Support

Manage multiple projects:

• Cross-project queries: "Show P0 issues across all projects"
• Project comparison: "Which project has the most overdue issues?"
• Resource allocation: "How are developers distributed across projects?"
• Portfolio planning: "Show all initiatives in the Engineering portfolio"

Atlassian Ecosystem Integration

Connect to other Atlassian tools:

• Confluence: "Pull requirements from Confluence page 'Mobile Spec'"
• Bitbucket: "Show PRs linked to BACKEND-456"
• Jira Service Management: "Create incident from bug PROD-789"
• Jira Align: "What OKRs are linked to this epic?"

Notifications and Alerts

Stay informed:

• Issue watching: "Watch all issues in Epic-45"
• Mentions: Get notified when someone @mentions you in comments
• Status changes: "Notify me when BACKEND-456 moves to QA"
• Custom alerts: "Alert me when any P0 bug is created"

Permissions and Security

Respects Jira's permission scheme:

• Project permissions: Only see projects you have access to
• Issue security levels: Confidential issues remain hidden
• Role-based access: Developers see different data than managers
• Audit logging: All queries and actions are logged

Setup Option 1: HeraClaw Cloud (Recommended)

Time required: 60 seconds Technical skill: None Cost: Included in HeraClaw Cloud subscription Best for: 95% of users, all team sizes

Why HeraClaw Cloud?

• No Atlassian Marketplace app registration
• No weeks-long marketplace approval wait
• No OAuth 2.0 configuration
• No webhook setup and management
• No server infrastructure to maintain
• No SSL certificates to renew
• No uptime monitoring needed
• Professional support included
• Automatic updates and security patches
• 99.9% uptime SLA
• Enterprise-grade security

Steps:

1. Sign up for HeraClaw Cloud

• Visit cloud.getopenclaw.ai
• Click "Sign In" (no credit card required)
• Create your account (takes 60 seconds)

2. Navigate to Integrations

• Click "Integrations" in the left sidebar
• Find "Jira" in the list
• Click "Connect to Jira"

3. Authorize the Connection

• Jira OAuth screen appears
• Select your Jira site from dropdown
• Review permissions (you can customize)
• Click "Accept"

4. Configure Project Access (Optional)

• Back in HeraClaw dashboard
• Choose which projects the assistant can access
• Set permissions (who can query data)
• Save configuration

5. Test the Integration

• In HeraClaw chat interface
• Type: "Show me my open Jira issues"
• You should see your issues listed

6. Start Using AI for Jira

• "What's my team's velocity?"
• "Create a bug for the login issue"
• "Show sprint burndown status"

That's it! You're up and running.

What You Get with HeraClaw Cloud:

✅ Instant Setup - No Atlassian Marketplace approval (saves 2-4 weeks) ✅ Automatic Updates - We handle Jira API changes ✅ Professional Support - Email, chat, and phone support ✅ 99.9% Uptime - SLA-backed reliability ✅ Enterprise Security - SOC 2, GDPR, HIPAA available ✅ Unlimited Projects - Connect as many as you need ✅ Advanced Features - Multi-site support, custom automation, audit logs ✅ No Maintenance - We manage servers, scaling, monitoring

Pricing: See cloud.getopenclaw.ai/pricing (starts with affordable team plans)

Get Started: Start with HeraClaw Cloud →

Setup Option 2: Self-Hosted (Advanced)

Time required: 45-60 minutes (first time), 20-30 minutes (if experienced) Technical skill: Advanced Cost: VPS hosting ($10-50/month) + your time Best for: DevOps engineers, technical teams, compliance requirements

Who should self-host?

✅ DevOps engineers who enjoy infrastructure ✅ Organizations with strict data residency requirements ✅ Teams already running Kubernetes/Docker infrastructure ✅ Technical enthusiasts with homelab setups ✅ Companies that cannot use third-party SaaS

Who should NOT self-host?

❌ Small teams without DevOps expertise ❌ Anyone who values time over cost savings ❌ Teams without 24/7 on-call coverage ❌ Organizations without security/compliance teams ❌ Anyone who wants to avoid 2-4 week Atlassian Marketplace approval

Prerequisites:

• OpenClaw installed and running (Mac/Linux/VPS)
• Terminal/SSH access to your OpenClaw server
• Jira Cloud or Jira Data Center admin permissions
• Understanding of OAuth 2.0
• Basic networking knowledge (ports, firewalls, reverse proxies)
• SSL certificate (for production)
• Important: Atlassian Marketplace approval (2-4 weeks for new apps)

Detailed Self-Hosted Setup

Important Note on Atlassian Marketplace:

If you're creating a custom Jira app (not using an existing one), you'll need Atlassian Marketplace approval. This process typically takes 2-4 weeks and requires:

• Security review
• Privacy policy
• Terms of service
• Support contact information
• App testing and validation

This is why 95% of teams choose HeraClaw Cloud - it bypasses this entire process.

If you still want to self-host, here's how:

Step 1: Create a Jira App (Atlassian Connect or OAuth 2.0)

Option A: OAuth 2.0 App (Recommended for self-hosted)

1. Go to developer.atlassian.com/console
2. Click "Create" → "OAuth 2.0 integration"
3. App Name: "OpenClaw Assistant" (or your preference)
4. Click "Create"

Option B: Atlassian Connect App (For advanced users)

1. Create an atlassian-connect.json descriptor
2. Host it on your server at /atlassian-connect.json
3. Register the app in Jira

We'll focus on OAuth 2.0 as it's simpler for self-hosted setups.

Step 2: Configure OAuth 2.0 Settings

1. In your app console, go to "Authorization"
2. Click "Add" under OAuth 2.0 (3LO)
3. Callback URL: https://your-openclaw-domain.com/jira/callback
   • Must be HTTPS in production
   • Must be publicly accessible
4. Click "Save changes"

Step 3: Add API Scopes

1. Go to "Permissions" tab
2. Click "Add" under Jira API
3. Add these scopes:

Required scopes:

• read:jira-work - Read project and issue data
• write:jira-work - Create and update issues
• read:jira-user - Read user information

Optional scopes (for advanced features):

• manage:jira-project - Manage projects and boards
• manage:jira-configuration - Manage workflows and fields
• delete:jira-work - Delete issues (use with caution)
• read:jira-webhook - Read webhook configurations
• write:jira-webhook - Create webhooks for real-time updates

1. Click "Save changes"

Step 4: Get OAuth Credentials

1. Go to "Settings" tab
2. Copy your Client ID (looks like abc123xyz...)
3. Click "Generate secret"
4. Copy your Client Secret (keep this secure!)
5. Save both - you'll need them for OpenClaw config

Step 5: Configure OpenClaw

Edit your OpenClaw config file (usually ~/.openclaw/config.yaml or ~/.config/openclaw/config.yaml):

channels:  jira:    enabled: true        # OAuth credentials from Step 4    clientId: "your-client-id-here"    clientSecret: "your-client-secret-here"        # Your Jira site URL    siteUrl: "https://yourcompany.atlassian.net"        # Callback URL (must match OAuth settings)    callbackUrl: "https://your-openclaw-domain.com/jira/callback"        # Optional: Restrict to specific projects    allowedProjects:      - "BACKEND"      - "MOBILE"      - "INFRA"        # Optional: Only these users can query Jira    allowedUsers:      - "user@company.com"      - "manager@company.com"        # Optional: Enable webhooks for real-time updates    webhooks:      enabled: true      events:        - "jira:issue_created"        - "jira:issue_updated"        - "jira:issue_deleted"        # Optional: Cache settings (improve performance)    cache:      enabled: true      ttl: 300  # 5 minutes

Step 6: Authorize OpenClaw to Access Jira

1. Start OpenClaw:

   bashCopy

   openclaw gateway start

2. OpenClaw will output an authorization URL:

   bashCopy

   Visit this URL to authorize Jira:https://auth.atlassian.com/authorize?client_id=...

3. Open the URL in your browser

4. Select your Jira site

5. Review permissions

6. Click "Accept"

7. You'll be redirected to your callback URL

8. OpenClaw will exchange the code for access tokens

Step 7: Verify the Connection

Check OpenClaw logs:

openclaw gateway logs --follow

You should see:

✓ Jira OAuth connected✓ Site: https://yourcompany.atlassian.net✓ Projects: BACKEND, MOBILE, INFRA (3 accessible)✓ User: admin@company.com

Step 8: Test the Integration

In OpenClaw chat interface:

1. Test query: "Show me my open Jira issues"

   • Should list your assigned issues

2. Test creation: "Create a test issue in the BACKEND project"

   • Should create issue and return the issue key

3. Test JQL: "Show all P0 bugs in the Mobile project"

   • Should execute JQL and return results

4. Test updates: "Add comment to BACKEND-123: Testing OpenClaw integration"

   • Should add comment successfully

If queries fail, check logs for errors.

Advanced Self-Hosted Configuration

Multiple Jira Sites

Run one OpenClaw instance across multiple Jira sites:

channels:  jira:    instances:      main_site:        siteUrl: "https://company.atlassian.net"        clientId: "client-id-1"        clientSecret: "secret-1"        allowedProjects:          - "BACKEND"          - "MOBILE"            client_site:        siteUrl: "https://client.atlassian.net"        clientId: "client-id-2"        clientSecret: "secret-2"        # Different project access for client site

Custom JQL Shortcuts

Define shortcuts for common queries:

channels:  jira:    shortcuts:      my_p0: "assignee = currentUser() AND priority = Highest AND resolution = Unresolved"      team_backlog: "project = BACKEND AND status = 'To Do' ORDER BY priority DESC"      current_sprint: "sprint in openSprints() AND project = MOBILE"

Use them: "Show my_p0" → Executes the saved JQL

Webhook Configuration

Receive real-time updates from Jira:

channels:  jira:    webhooks:      enabled: true      endpoint: "https://your-openclaw-domain.com/jira/webhook"      secret: "your-webhook-secret"  # Verify webhook authenticity      events:        - "jira:issue_created"        - "jira:issue_updated"        - "jira:issue_deleted"        - "comment_created"            # Optional: Filters (only process certain events)      filters:        projects:          - "BACKEND"          - "MOBILE"        issueTypes:          - "Bug"          - "Story"

With webhooks enabled, OpenClaw can:

• Notify team when P0 bugs are created
• Alert when sprint issues are updated
• Trigger workflows based on Jira events

Project-Specific Configurations

Different behavior per project:

channels:  jira:    projectConfigs:      # Backend project: detailed technical queries      "BACKEND":        allowedQueries:          - "jql"          - "issue_details"          - "sprint_reports"        queryDepth: "detailed"  # Include all fields            # Mobile project: simplified view      "MOBILE":        allowedQueries:          - "basic_search"          - "issue_status"        queryDepth: "summary"  # Basic fields only

Rate Limiting

Protect against Jira API rate limits:

channels:  jira:    rateLimit:      # Jira Cloud rate limits: 10 requests/second (burst), sustained lower      requestsPerSecond: 5      burstAllowance: 10            # Per-user limits      perUser:        requests: 100        window: 60  # seconds            # Global limits      global:        requests: 500        window: 60

Issue Creation Templates

Predefine issue templates:

channels:  jira:    templates:      bug:        project: "BACKEND"        issueType: "Bug"        priority: "Medium"        labels:          - "needs-triage"        customFields:          "customfield_10001": "Production"  # Environment            feature:        project: "MOBILE"        issueType: "Story"        priority: "Low"        labels:          - "feature-request"

Use them: "Create a bug using the bug template: Login fails on iOS"

Custom Field Mappings

Map custom field IDs to friendly names:

channels:  jira:    customFields:      "customfield_10001": "Customer Impact"      "customfield_10002": "Legal Approval"      "customfield_10003": "Security Review"      "customfield_10004": "Original Estimate"

Query them: "Show issues where Customer Impact is High"

Automation Rules

Automate common workflows:

channels:  jira:    automation:      rules:        # Auto-assign P0 bugs        - trigger: "issue_created"          conditions:            - field: "priority"              equals: "Highest"            - field: "issueType"              equals: "Bug"          actions:            - type: "assign"              assignee: "oncall-engineer"            - type: "notify"              channel: "#engineering-urgent"                # Auto-label customer-facing issues        - trigger: "issue_created"          conditions:            - field: "customfield_10001"  # Customer Impact              equals: "High"          actions:            - type: "add_label"              label: "customer-facing"

Troubleshooting Self-Hosted Setup

OAuth Authorization Fails

Symptoms: Click "Accept" but get redirect error

Potential causes:

1. Callback URL mismatch
2. Client secret incorrect
3. HTTPS required but using HTTP
4. Firewall blocking callback

Fix:

# Verify callback URL matches OAuth settings exactly# Check config.yaml callbackUrl vs developer console# Test callback endpoint is accessiblecurl https://your-openclaw-domain.com/jira/callback# Check OpenClaw logs for errorsopenclaw gateway logs | grep -i oauth

"Insufficient Permissions" Error

Symptoms: Queries fail with permission errors

Potential causes:

1. Missing OAuth scopes
2. Project permissions in Jira
3. User doesn't have access to project

Fix:

1. Go to developer.atlassian.com/console → Your App → Permissions
2. Add required scopes (error message tells you which)
3. Re-authorize the connection
4. Verify Jira project permissions for your user

Rate Limit Errors

Symptoms: Logs show "rate_limited" or "429 Too Many Requests"

Potential causes:

1. Too many API calls in short time
2. Jira Cloud rate limits (10 req/sec burst)
3. Other integrations also using API

Fix:

# Configure stricter rate limiting in OpenClawchannels:  jira:    rateLimit:      requestsPerSecond: 3  # Conservative limit      burstAllowance: 5          # Enable caching to reduce API calls    cache:      enabled: true      ttl: 300  # 5 minutes

Webhook Not Receiving Events

Symptoms: Webhooks configured but no events received

Potential causes:

1. Webhook URL not publicly accessible
2. HTTPS required
3. Webhook not registered in Jira
4. Firewall blocking Atlassian IPs

Fix:

# Test webhook endpoint is accessiblecurl -X POST https://your-openclaw-domain.com/jira/webhook \  -H "Content-Type: application/json" \  -d '{"test": "data"}'# Verify webhook is registered in Jira:# Jira → Settings → System → Webhooks# Check OpenClaw logsopenclaw gateway logs | grep -i webhook

JQL Queries Return Empty Results

Symptoms: Valid JQL returns no results in OpenClaw but works in Jira

Potential causes:

1. Project filter in config
2. User permissions different than expected
3. JQL syntax error

Fix:

# Test JQL directly via Jira APIcurl -u email@example.com:api-token \  'https://yoursite.atlassian.net/rest/api/3/search?jql=project=BACKEND'# Check allowed projects in configgrep -A 5 'allowedProjects' ~/.openclaw/config.yaml# Verify user has project access in Jira

Slow Query Performance

Symptoms: Queries take 10+ seconds to return results

Potential causes:

1. Large result sets
2. Complex JQL
3. No caching
4. Network latency

Fix:

channels:  jira:    # Enable caching    cache:      enabled: true      ttl: 300  # 5 minutes        # Limit result sets    maxResults: 50  # Don't fetch more than 50 issues        # Pagination for large queries    pagination:      enabled: true      pageSize: 25

Custom Fields Not Displaying

Symptoms: Custom fields don't appear in results

Potential causes:

1. Custom field ID not mapped
2. Field not included in query
3. User doesn't have permission to view field

Fix:

# Map custom fields to friendly nameschannels:  jira:    customFields:      "customfield_10001": "Customer Impact"      "customfield_10002": "Legal Approval"        # Include all fields in queries    includeFields:      - "*all"  # Include all standard fields      - "customfield_*"  # Include all custom fields

Connection Drops Randomly

Symptoms: Integration works, then stops, then works again

Potential causes:

1. Access token expired
2. Refresh token not working
3. Network issues
4. OpenClaw restarting

Fix:

# Check token expiryopenclaw gateway status --verbose# Force token refreshopenclaw jira refresh-token# Enable auto-refresh in configchannels:  jira:    auth:      autoRefresh: true      refreshBeforeExpiry: 3600  # Refresh 1 hour before expiry

Security Best Practices for Self-Hosted

1. Protect Your OAuth Credentials

# Never commit credentials to gitecho "config.yaml" >> .gitignore# Use environment variablesexport JIRA_CLIENT_ID="your-client-id"export JIRA_CLIENT_SECRET="your-client-secret"# Reference in configchannels:  jira:    clientId: ${JIRA_CLIENT_ID}    clientSecret: ${JIRA_CLIENT_SECRET}# Or use secrets managementchannels:  jira:    clientId: "op://Work/Jira OAuth/client_id"  # 1Password    clientSecret: "op://Work/Jira OAuth/client_secret"

2. Use HTTPS Everywhere

Jira OAuth requires HTTPS:

• Callback URLs must use HTTPS
• Webhook endpoints must use HTTPS
• Use Let's Encrypt for free SSL certificates

# Get free SSL cert with certbotsudo certbot --nginx -d your-openclaw-domain.com

3. Implement Access Controls

channels:  jira:    # Only allow specific users    allowedUsers:      - "manager@company.com"      - "engineer@company.com"        # Only specific projects    allowedProjects:      - "BACKEND"      - "MOBILE"        # Block sensitive projects    blockedProjects:      - "SECURITY"  # Security team only      - "HR"  # HR team only

4. Enable Audit Logging

logging:  audit:    enabled: true    logFile: "/var/log/openclaw/jira-audit.log"    includeQueries: true  # Log JQL queries    includeResults: false  # Don't log issue data (privacy)    includeMetadata: true  # Log who, when, what project

5. Rotate OAuth Tokens Regularly

1. Every 90 days, regenerate OAuth credentials
2. Go to developer.atlassian.com/console → Your App → Settings
3. Click "Regenerate secret"
4. Update OpenClaw config
5. Re-authorize the connection

6. Monitor for Abuse

channels:  jira:    monitoring:      alertOnHighUsage: true      threshold: 500  # queries per hour      notifyEmail: "security@company.com"            # Track suspicious patterns      detectAnomalies: true      alertOnBulkDeletes: true  # Alert if someone tries to delete many issues

7. Principle of Least Privilege

Only add OAuth scopes you actually need:

• Don't add delete:jira-work unless you need delete functionality
• Don't add manage:jira-project if you only need to read/write issues
• Review scopes quarterly and remove unused ones

8. Verify Webhook Authenticity

channels:  jira:    webhooks:      enabled: true      secret: "your-webhook-secret"  # Atlassian signs webhooks      verifySignature: true  # Verify signature matches      allowedIPs:        - "13.52.5.0/24"  # Atlassian IP ranges        - "13.236.8.0/25"

Comparison: HeraClaw Cloud vs Self-Hosted

Why 95% of users choose HeraClaw Cloud:

✅ Skip marketplace approval - 2-4 weeks saved, no rejection risk ✅ Time is valuable - 45-60 min setup + ongoing maintenance adds up ✅ Jira API changes frequently - We handle breaking changes automatically ✅ Security is hard - SOC 2 compliance takes months and $$$ to achieve ✅ Reliability matters - 99.9% SLA vs DIY uptime monitoring ✅ Support is worth it - Email/chat/phone support when things break ✅ Hidden costs - SSL certs, monitoring tools, incident response time

When self-hosting makes sense:

✅ You have DevOps engineers with spare capacity ✅ Data cannot leave your infrastructure (compliance) ✅ You're already running Kubernetes/Docker setups ✅ You want to heavily customize the codebase ✅ You have 24/7 on-call rotation to handle incidents ✅ You already have an approved Atlassian Marketplace app

Frequently Asked Questions

Q: Do I need Jira Cloud or can I use Jira Server/Data Center?

A: HeraClaw Cloud supports Jira Cloud primarily. Jira Data Center support available for enterprise customers. Self-hosted OpenClaw supports both Jira Cloud and Jira Data Center with OAuth 2.0.

Note: Jira Server is deprecated by Atlassian (end-of-life Feb 2024). Migrate to Jira Cloud or Data Center.

Q: How long does Atlassian Marketplace approval take?

A: 2-4 weeks on average, sometimes longer if issues are found during security review. This is the main reason teams choose HeraClaw Cloud - it completely bypasses this process.

Q: Can I use this with multiple Jira sites?

A: Yes! HeraClaw Cloud supports unlimited Jira sites. Self-hosted requires configuring each site separately.

Q: What permissions does the integration need?

A: Minimum: Read projects and issues, create/update issues, read users. Optional: Manage projects, delete issues, manage webhooks. Full list in setup guide above.

Q: Can I restrict which projects the assistant can access?

A: Yes. Configure project-level access (only certain projects), user-based access (specific users), or role-based (only project admins).

Q: Does it work with Jira Software, Jira Service Management, and Jira Work Management?

A: Yes, all three Jira products are supported. The integration adapts to your Jira product type.

Q: Can it handle custom fields?

A: Yes. The assistant auto-detects custom fields and allows you to query/update them by name. You can also map custom field IDs to friendly names.

Q: What about Jira workflows?

A: Full support. The assistant respects your workflow transitions, required fields, and validators. It won't allow invalid status transitions.

Q: Is my data secure?

A: HeraClaw Cloud: SOC 2 Type II certified, encrypted in transit (TLS 1.3) and at rest (AES-256), GDPR compliant. Self-hosted: Your responsibility, but you control the infrastructure.

Q: Can it create complex issues with attachments, links, etc.?

A: Yes. Create issues with:

• Attachments (files, images, documents)
• Issue links (blocks, relates to, duplicates)
• Sub-tasks
• Epic links
• Sprint assignments
• Custom fields
• Watchers
• Labels and components

Q: What if Jira changes their API?

A: HeraClaw Cloud: We handle all API changes automatically with zero downtime. Self-hosted: You must update OpenClaw manually when breaking changes occur.

Q: How fast are responses?

A: Typically 1-3 seconds from query to response, depending on:

• Query complexity (simple JQL vs complex aggregations)
• Result set size (10 issues vs 1000 issues)
• Jira API latency (varies by region)
• Caching (cached queries return in milliseconds)

Q: Can I use JQL directly or do I have to use natural language?

A: Both! You can:

• Use natural language: "Show P0 bugs assigned to me"
• Use raw JQL: project = BACKEND AND priority = Highest AND assignee = currentUser()
• Mix both: "Execute this JQL: [complex query]"

Q: Does it support Agile boards (Scrum/Kanban)?

A: Yes. Full support for:

• Sprint boards (Scrum)
• Kanban boards
• Backlog management
• Sprint reports (burndown, velocity)
• Board filters and quick filters

Q: Can I migrate from self-hosted to Cloud?

A: Absolutely. Export your configuration, sign up for HeraClaw Cloud, import your settings. We'll help you migrate in under 15 minutes. Most users who migrate never go back (and save 2-4 weeks by skipping marketplace approval).

Q: What about Jira rate limits?

A: Jira Cloud limits apps to approximately 10 requests/second (burst), with lower sustained rates. OpenClaw handles this automatically by:

• Request queuing
• Intelligent caching
• Batch operations
• Rate limit backoff

You won't hit rate limits under normal usage.

Q: Can it handle bulk operations?

A: Yes. Bulk operations like:

• "Add label 'urgent' to all P0 bugs in BACKEND project"
• "Move all 'Ready for QA' issues to 'In QA'"
• "Assign all unassigned issues in current sprint to the team lead"

Bulk operations are performed with rate limiting to avoid API limits.

Q: What about JQL auto-completion?

A: The assistant suggests JQL completions as you type and validates JQL syntax before executing. Invalid JQL returns helpful error messages.

Q: Can it integrate with other tools (GitHub, Slack, Confluence)?

A: Yes. If you use GitHub, Slack, Confluence, or other tools, OpenClaw can reference that data (e.g., "Show Jira issues linked to GitHub PR #123").

Q: Does it work with Jira Automation rules?

A: Yes. OpenClaw actions trigger Jira Automation rules just like manual actions would. You can also query automation rule execution history.

Q: What about issue security levels?

A: Fully supported. Issues with security levels are only visible to users with appropriate permissions. OpenClaw respects all Jira security schemes.

Q: Can I customize the assistant's responses?

A: Yes. Configure:

• Response verbosity (detailed vs summary)
• Default JQL ordering
• Issue field display preferences
• Date/time formats
• Notification preferences

Q: How do I remove the integration?

A: HeraClaw Cloud: Settings → Integrations → Jira → Disconnect. Self-hosted: Revoke OAuth access in Atlassian, disable in OpenClaw config.

Q: Does it support Jira Cloud multi-tenancy?

A: Yes. Manage multiple Jira Cloud sites from one OpenClaw instance, with different permissions and configurations per site.

Q: What about compliance (SOC 2, GDPR, HIPAA)?

A: HeraClaw Cloud: SOC 2 Type II certified, GDPR compliant, HIPAA available for enterprise customers. Full audit logs and data processing agreements available.

Get Started

For 95% of users (recommended):

Start with HeraClaw Cloud →

• 60-second setup
• No Atlassian Marketplace approval (save 2-4 weeks)
• No technical skills needed
• Professional support
• 99.9% uptime SLA
• No credit card required

For advanced users only:

Self-Hosting Setup Guide →

• 45-60 minute setup
• Requires DevOps skills
• 2-4 week marketplace approval wait
• You maintain infrastructure
• Full control and customization

Questions? Email support@cloud.getopenclaw.ai or join our community Slack for help.

Last updated: April 10, 2026

Built with OpenClaw — The open-source AI assistant platform. Self-host or use HeraClaw Cloud.