Jira Issues
Project ManagementConnect operational workflows to your engineering and project tracking. Agents create, update, transition, assign, and search Jira issues. Full JQL query support and comment and attachment management.
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
With FlowRunner
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 Capabilities
13 actionsIssue 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.
Start building with Jira Issues
$100 in credits. No card required. Connect in minutes.