--- title: "Jira Issues Integration" description: "Connect operational workflows to your engineering and project tracking. Agents create, update, transition, assign, and search Jira issues. Full JQL query support." url: https://flowrunner.ai/integrations/jira-issues date_modified: 2026-08-01T02:40:32-07:00 --- # Jira Issues [Project Management](https://flowrunner.ai/integrations/category/project-management-productivity) Connect operational workflows to your engineering and project tracking. Agents create, update, transition, assign, and search Jira issues. Full JQL query support. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 13 actions · Basic auth · available [Jira Issues website](https://id.atlassian.com/) · Capability data verified 2026-08-04 1. Customer sends email flagging a critical issue to support inbox 2. Parseur or Mailbox integration processes the email for structured data 3. Agent creates Jira issue with customer name, description, and severity level 4. Agent attaches original email and assigns to on-call engineer 5. Engineer receives Slack message with Jira issue link and priority 6. P1 issues above severity threshold routed to team lead for assignment confirmation ## What This Integration Enables Jira integration gives FlowRunner agents the ability to create and manage issues, transition them through workflow states, add comments and attachments, and query across projects using JQL. Agents use Jira as the coordination layer between operational events and the teams responsible for resolving them. ### Without FlowRunner **Manual ticket creation**: Support staff read each email and create Jira tickets by hand **Context-free tickets**: Engineers receive tickets with a subject line and no structured data **Slow sprint visibility**: Engineering manager checks Jira manually to find unassigned or blocked issues ### With FlowRunner **Ticket created before email is read**: Jira issue with full context created and assigned within seconds of receipt **Structured tickets every time**: Customer name, issue description, severity, and source email attached automatically **Daily sprint health alerts**: Unassigned and blocked issues surfaced to engineering channel each morning ## Use Case Scenarios ### Customer Escalation to Jira A customer sends an email flagging a critical issue. Parseur or the Mailbox integration processes the email. The agent creates a Jira issue in the Support project with the customer name, issue description, and severity based on keywords. It attaches the original email. It assigns the issue to the on-call support engineer based on rotation data. It sends a Slack message to the engineer: "New P1 issue created: \[Issue Summary\]. Jira: \[link\]." The engineer has a tracked, assigned issue before anyone manually reads the email. ### Operational Exception Tracking A payment processing workflow detects an error that requires engineering investigation. The agent creates a Jira bug report with the full error context: timestamp, error code, affected transaction ID, and steps to reproduce. It links the issue to the relevant payment in Stripe. It adds a comment with the workflow execution trace. When the engineering team resolves the issue, On Transition Issue (via the agent polling status changes) fires, and the agent logs the resolution in the payment audit trail. ### Sprint Monitoring and Escalation Every day at 9am, an agent runs a JQL query: issues in the current sprint that are unassigned, or issues flagged as blocked. It posts a summary to the #engineering-daily Slack channel: "3 sprint items are unassigned. 2 issues are blocked. Sprint ends in 4 days." It tags the engineering manager for awareness. The team has visibility into sprint health without anyone building a status report. ## Human-in-Loop Highlight When an agent is about to create a Jira issue that would be assigned to a specific person, it does not assume the assignment is correct for high-impact issues. For issues above a certain priority level or involving specific sensitive components, it routes the assignment decision via Slack: "New P1 issue ready to create: \[Summary\]. Assign to \[Suggested Assignee\] based on rotation, or do you want to assign someone else?" The team lead confirms or redirects. Critical issues have accountable ownership from the moment they are created. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 13 actions ### Issue Management 7 - **Create Issue** Creates a new Jira issue with support for custom fields, priority, assignee, and components. Used when any external event requires tracking in Jira: a customer escalation creates a support issue, a system error creates a bug report, an operational exception creates a task for the responsible team. - **Get Issue** Retrieves a specific issue with full field detail. Used to check status, read comments, or retrieve metadata before taking action in connected workflows. - **Update Issue** Modifies fields on an existing issue: summary, description, priority, custom fields. Used when issue details change or additional context needs to be added after creation. - **Delete Issue** Removes an issue. Used in cleanup workflows when a ticket was created in error. - **Search Issues** Executes a JQL query and returns matching issues. JQL (Jira Query Language) supports complex filtering: by project, assignee, status, priority, label, creation date, and custom fields. Used in reporting, escalation monitoring, and batch update workflows. - **Transition Issue** Moves an issue to a different workflow status: Open to In Progress, In Progress to Done. Used to keep Jira state synchronized with external events: when a customer confirms their issue is resolved, the agent transitions the Jira ticket to Done automatically. - **Assign Issue** Assigns or unassigns an issue to a team member. Used in routing workflows where the agent determines the appropriate owner based on issue type, component, or workload. ### Comments 4 - **Add Comment** Posts a comment to an issue. Used to log agent activity, add context from external systems, and notify watchers of updates. Comments support Atlassian Document Format (ADF) for rich formatting. - **Get Comments** Retrieves all comments on an issue. Used when agents need to read the conversation history before adding context or taking action. - **Update Comment** Modifies an existing comment. Used for correction workflows. - **Delete Comment** Removes a comment. ### Attachments 1 - **Add Attachment** Attaches a file to a Jira issue. Used to add evidence, screenshots, logs, and supporting documents directly to issues from the workflow. ### Projects 1 - **Get Project** Retrieves project configuration and metadata. Used when agents need project context (available issue types, components, workflow states) before creating issues. ## Frequently Asked Questions ### What can FlowRunner do with Jira Issues? FlowRunner agents can run Create Issue, Get Issue, and Update Issue in Jira Issues, plus 10 more actions. ### Does connecting Jira Issues to FlowRunner require OAuth? No. Jira Issues connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can Jira Issues trigger a FlowRunner workflow automatically? Jira Issues doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Jira Issues?** This integration exposes Jira Issues to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/jira-issues. Site index: https://flowrunner.ai/llms.txt