← Tools

Jira

A project and issue tracking tool.

Official source ↗ · Source checked 2026-10-23

Check official pricing and availability. Model versions must be checked in each case.

Models, versions and aliases in cases

These labels share this page. Original identifiers are preserved; versions may differ in capability or availability.

Find a workflow with this tool →

Tasks covered in this library

9 tag-associated cases; tool roles have not all been reviewed. This is not the product’s full capability range.

Latest case update:2026-10-26

Workflows, prerequisites & evidence

Work & Operations

Jira MCP Server: Manage Jira tickets with natural language

Import n8n template → configure Jira credentials and MCP trigger → connect Claude Desktop to local MCP → create/update/query tickets via conversation

Read the case’s method and prerequisites

Prerequisites: Jira Cloud admin account, n8n instance with Langchain and MCP nodes, Claude Desktop or MCP-compatible AI assistant. Cost: Jira Cloud subscription + n8n self-hosted/cloud plan. Note: all tool nodes in workflow.json have empty parameters objects; field mappings must be configured manually.

n8n · Jira

Associated by case tags. Verify costs, permissions and actual results in the case.

Work & Operations

Natural-Language Chat-Driven Jira Issue Management: n8n + Gemini + MCP

Send chat messages to n8n, let Gemini interpret intent, and execute Jira operations via an MCP server

Read the case’s method and prerequisites

Prerequisites: n8n instance (cloud or self-hosted), Jira Software account with API token, Google Gemini API credentials, a configured and accessible MCP server. Basic n8n workflow experience recommended.

n8n · Jira

Associated by case tags. Verify costs, permissions and actual results in the case.

Work & Operations

Auto-generate Lessons Learned reports from Jira Epics to Google Docs

Jira Epic marked Done → fetch related issues and comments → AI generates structured Lessons Learned report → write to designated Google Docs document

Read the case’s method and prerequisites

Requires an n8n instance, Jira Cloud API credentials, OpenAI API credentials, Google Docs OAuth2 credentials, and a target Google Docs document ID. The template uses gpt-4o-mini by default and supports switching to other models in the same family. The AI Agent relies on a System Message to define output format; Simple Memory provides a conversational window.

n8n · jira · google-docs

Associated by case tags. Verify costs, permissions and actual results in the case.

Work & Operations

Automatically create JIRA issues from Outlook email support requests

Scheduled poll of Outlook shared inbox → AI triage → auto-create JIRA issues with labels and priority

Read the case’s method and prerequisites

Prerequisites: n8n instance; Outlook shared inbox (recommended dedicated to support); OpenAI API key; JIRA Cloud project access. Three credentials required: microsoftOutlookOAuth2Api, openAiApi, jiraSoftwareCloudApi. Template runs hourly by default, fetching the last hour of mail. JIRA project/issueType defaults of 10000 must be replaced with actual IDs.

n8n · jira · outlook

Associated by case tags. Verify costs, permissions and actual results in the case.

Work & Operations

n8n Automated Support Ticket Triage & Resolution: JIRA + OpenAI Template

Scheduled JIRA To Do pull → AI auto-labeling / priority / description rewrite → retrieve similar resolved issues → generate suggested fix as ticket comment

Read the case’s method and prerequisites

Prerequisites: accessible n8n instance; JIRA Cloud account with jiraSoftwareCloudApi credential; OpenAI API key with openAiApi credential. Default model is gpt-4o-mini (explicit in nodes), with gpt-4o as alternative. JIRA project must exist or adjust JQL from `Project = 'SUPPORT'`. Polling frequency set via Schedule Trigger minutes field (value must be configured). Before activation, customize the label list in the Label, Prioritize & Rewrite system prompt to match your organization's taxonomy.

n8n · jira

Associated by case tags. Verify costs, permissions and actual results in the case.

Software & DevOps

n8n Automated Jira Ticket Responses with GPT-4 and Pinecone

Scheduled trigger → query assigned Jira issues → retrieve from Pinecone knowledge base → AI generates reply → auto-post Jira comment

Read the case’s method and prerequisites

Prerequisites: n8n instance; Jira API access (API token + email); Pinecone account (API key + environment); OpenAI API key. A pre-indexed knowledge base must exist in Pinecone. The workflow runs on Schedule Trigger at defined intervals, not via real-time webhook.

n8n · jira · pinecone

Associated by case tags. Verify costs, permissions and actual results in the case.

Sales, Marketing & Support

PagerDuty-Port AI Incident Lifecycle Automation in n8n

PagerDuty webhook events → Port software catalog context → OpenAI severity assessment → Slack tiered alerts & Jira tickets → post-resolution MTTR calculation & post-mortem automation

Read the case’s method and prerequisites

Prerequisites: self-hosted n8n instance (template explicitly states Self-Hosted only); Port account with software catalog configured (services, on-call schedules, deployment history); PagerDuty with webhook capabilities; Jira Cloud project permissions; Slack workspace bot permissions; OpenAI API key. Required credentials: portIoApi, openAiApi, slackApi, jiraSoftwareCloudApi. Costs: billed per respective platform pricing; OpenAI charged by token usage.

n8n · slack · jira · port

Associated by case tags. Verify costs, permissions and actual results in the case.

Software & DevOps

Bug Repro Pack Builder: Turn Vague Bug Reports into Reproducible Step Packs

Input vague bug report with screenshot → separate stated facts from assumptions, record precise environment, reproduce step-by-step on staging with synthetic data → output reproducible pack with evidence or non-reproducible finding

Read the case’s method and prerequisites

Prerequisites: access to a staging environment with ability to create synthetic test data; grok-bot runtime available. Constraints: strictly prohibited from using production customer data, querying production databases, signing into real customer accounts, or copying real records into staging. Tool integrations (jira/github/sentry) are source-suggested labels only; actual connector configuration required separately. Cost conditions unknown.

jira · github · sentry

Associated by case tags. Verify costs, permissions and actual results in the case.

Work & Operations

n8n AI-Powered Bug Triage: Webhook Ingests Reports, GPT-4 Analyzes, Creates Jira Issues, and Alerts Slack

External system POSTs bug suspicion via Webhook → OpenAI (GPT-4) analyzes priority and category → Switch routes to High/Medium/Low Jira creation nodes → Slack pushes to different channels by priority

Read the case’s method and prerequisites

Prerequisites: n8n instance (cloud or self-hosted); Jira account with permission to create Bug issues in project APP (customizable); OpenAI API credentials; Slack workspace and Bot token; ability to send POST requests to the n8n Webhook endpoint. Cost conditions unknown. Known limitations: the actual system/user prompt inside the OpenAI node is not disclosed in the source; the Webhook path is inconsistent between Quick Start (advanced-bug-triage) and Step 1 (bug-suspicion), workflow.json uses advanced-bug-triage; Priority Switch value1 is ={{$json.priority}} with fallbackOutput=1; the Jira summary expression starts with '=' as n8n expression syntax.

n8n · jira · slack

Associated by case tags. Verify costs, permissions and actual results in the case.