Connect Jira to your factory

Connect Jira Cloud to your factory so your team can start factory work without leaving Jira. When someone assigns or mentions Warp on a work item, Jira starts a Rovo agent session, a factory automation routes the request to the agent you chose, and the same session shows progress and the final result.

Prerequisites

• Jira Cloud - The integration supports Jira Cloud only, not Jira Server or Data Center.
• A Jira site admin - Installing the Warp app on a Jira site and connecting it to a Warp workspace requires site admin permissions.
• A factory - You need a factory in the connected workspace and permission to edit its definition.
• Rovo access - The Warp agent must be available on your Jira site so people can assign or mention it on work items.

Connect Jira and add an automation

1. Install the Warp app and connect it to your Warp workspace by following the Jira integration setup. Stop once the workspace is connected and return here; the label-triggered run steps on that page don’t apply to factories. The connected installation is available to every factory in the workspace.

2. Add a Jira automation to your factory definition. The control room’s automation editor doesn’t include the Jira trigger, so configure it with definitions as code: declare the jira integration for the factory, then create an automation that listens for the agent_session_created event. The agent field names the factory agent that handles matching requests.

   automations/jira-assignment/automation.md

   ---
   enabled: true
   agent: foreman
   triggers:
     - provider: jira
       event: agent_session_created
       filter:
         project_keys: [ENG]
         keywords: [investigate, fix]
   ---
   
   Handle the Jira assignment and return a concise result.

   With this automation, the agent named foreman handles sessions for work items in the ENG project whose assignment text contains investigate or fix.

   If you selected Jira projects when you created the factory, Warp already added this automation at automations/jira-agent-sessions/automation.md, scoped to those projects. Edit that file instead of creating a second automation.

3. Apply the definition, then test it: assign or mention Warp on a work item and include an instruction. Jira starts an agent session, and the run appears under the matching automation in your factory.

Filter which sessions start runs

All Jira work reaches the factory through a single event, agent_session_created, which fires when someone assigns or mentions Warp on a work item. A session starts a run only when it matches an enabled automation. Use the trigger’s filter to narrow what matches:

• project_keys - Match work items in these Jira projects.
• keywords - Match assignment text that contains any of these words. Matching is case-insensitive.

A session must match every field you set; within a field, any listed value is a match. Omit a field to match everything.

Caution

Filters decide which sessions start runs; they don’t limit access. The Warp app’s authorization in Jira controls which site and projects agents can read and update, so grant the app only the access the factory’s work requires.

What happens during a run

The agent starts with the assignment text and the work item it came from. When the factory declares Jira as an integration, the agent can also read the work item’s details, comments, and available workflow transitions.

Jira shows the task’s status as it progresses: submitted, working, waiting for input, completed, failed, or canceled. Replies in the same Rovo session continue the same run, even after the agent finishes a turn, so you can answer questions or add direction mid-task. A new session on the same work item starts a separate run.

When the run finishes, the agent posts its result in the Rovo session. It doesn’t comment on the work item unless you ask it to. The agent can act in Jira when asked: update the work item, post or edit comments, change workflow status, add or remove labels, or reassign it. State the actions you want in the automation instructions or the assignment; Jira permissions and valid workflow transitions apply to everything the agent does.

Permissions and reliability

• Runs act as the factory agent - A run executes as the agent selected by the automation, not as the Jira user who started the session.
• Repeated deliveries don’t repeat runs - Atlassian occasionally redelivers a Rovo message, and Warp treats redelivered copies as one request. Prefer instructions that check state before writing anyway, such as looking for an existing comment or label before adding one.
• Code changes follow repository policy - The Jira connection doesn’t grant code access. Pull request review and merge requirements come from your repositories and factory workflow.

Troubleshooting

• Warp is unavailable in Jira - Confirm the Warp app is installed on the Jira Cloud site. On the app’s Configure page, click Connect to Warp if the installation isn’t connected to a workspace.
• No run starts - Confirm an enabled agent_session_created automation exists, its agent is available, and its project and keyword filters match the assignment.
• The session shows no result - Open the matching automation’s run to see whether the agent is still working, waiting for input, or failed.
• A Jira update fails - Confirm the app can access the work item’s project and that the requested action or workflow transition is valid.

For the other ways to route work into a factory, see connecting your factory.