Skip to main content
The Jira integration connects your Atlassian Jira site to Modem. It captures issue and comment activity in real time so it can be analyzed and linked to the people behind it, and it gives the Modem Agent the ability to search, create, update, and comment on issues directly from chat.
Jira integration is currently in beta. Features and behavior may change.
One Jira connection covers every project on your site. If you use Jira Service Management (service desk) projects, their request conversations are captured as support tickets instead of issues — see the Jira Service Desk page for how those are handled.

​
Prerequisites

  • Admin access in the Modem organization where you want to connect Jira
  • Access to the Atlassian Jira site you want to connect, with permission to authorize apps
  • A Modem organization on a plan that includes Jira

​
Setup

1

Start the connection

Go to Settings → Integrations → Jira in your Modem dashboard and click Connect Jira.
2

Authorize Modem

You’ll be redirected to Atlassian to authorize Modem. Review the requested permissions, choose the Jira site you want to connect, and approve.
3

Choose projects to monitor

Back in Modem, pick which Jira projects to monitor from the project list. You can filter by project type (Software, Service, Business, Discovery) and toggle projects on or off at any time. Start narrow and expand as needed.
After authorization, Modem registers a webhook on your Jira site and begins receiving activity for the projects you selected.
Connecting more than one Atlassian site? Each site is its own Modem connection. Run the connect flow again and select the other site when Atlassian asks which one to authorize.

​
What Gets Captured

​
Issues and comments

Modem captures issue activity for your monitored projects as it happens:
  • New and updated issues
  • Comments added or edited on those issues
The issue summary is used as the title for each captured conversation, so it shows up under a readable heading, with comments threaded beneath it.

​
Issue metadata

Each captured update is stored alongside the current state of its issue, including:
  • Status and status category (e.g. To Do, In Progress, Done)
  • Issue type (bug, story, task, etc.) and priority
  • Reporter / creator and assignee
  • Created and updated timestamps
  • Jira issue URL for jumping back to the source issue

​
People

Modem resolves issue authors to Modem people profiles using their email address when Jira returns one. This gives you a unified view of each person’s activity across Jira and your other connected sources, and rolls activity up to the companies behind them.

​
Real-Time Capture

Jira capture is real-time: Modem starts ingesting activity from the moment you connect and select projects. New issues and comments are captured as Jira sends webhook events. There is no historical backfill of past issues today.

​
What the Agent Can Do

With Jira connected, you can ask the Modem Agent to work with your issues. Read operations run on demand; write operations require your approval before they execute.
  • Search issues by keyword, project, status, or raw JQL
  • List projects on your connected site
  • Read full issue details by key (e.g. ENG-123)
  • Create or update issues from feedback conversations (requires approval)
  • Add comments to existing issues (requires approval)
  • Link Modem topics to existing Jira issues
Write actions (creating or updating issues, adding comments) always ask for your approval before they run. Read actions like search and lookups run without a prompt.

​
Example Prompts

These work from the dashboard, Slack DMs, or by mentioning @modem in a channel. Simple: Advanced:
With the Slack integration installed, you can do all of this directly from Slack by messaging the Modem bot, no need to leave your conversation.

​
Troubleshooting

First confirm the integration shows a healthy status in Settings → Integrations → Jira, and that the relevant project is toggled on in the project list. Then allow a few minutes for webhook delivery and processing, and make sure the issue had a change (new issue, update, or comment) since connecting.
Open Settings → Integrations → Jira to see the error detail. If Modem prompts you to Authorize or Re-authorize, the access has expired or the required permissions changed; click through to grant access again. If the error persists, contact support@modem.dev.
  • Verify Jira is connected and healthy in Settings → Integrations → Jira - Make sure the issue exists on the site you connected - Be specific with project keys or names - Remember that creating issues and adding comments require approval, so check for a pending approval prompt
Issue authors are matched to Modem people by email address. If Jira doesn’t return an email for the author, their activity won’t be linked automatically.

​
Disconnecting

To disconnect Jira:
  1. Go to Settings → Integrations → Jira
  2. Click Disconnect
This removes the connection and deletes the webhook from your Jira site, so new activity is no longer synced and the agent can no longer act on Jira. Historical data remains in Modem after disconnecting.
https://mintcdn.com/modem-844d7a4a/LmhsPduwU_kokopO/icons/jira-service-desk.svg?fit=max&auto=format&n=LmhsPduwU_kokopO&q=85&s=b3d97dc2e46bf9447a77408d2b91b5f9

Jira Service Desk

Capture customer support requests from Jira Service Management projects.
https://mintcdn.com/modem-844d7a4a/Wr2r4IRr97lNQiQb/icons/link.svg?fit=max&auto=format&n=Wr2r4IRr97lNQiQb&q=85&s=e774d33588635d44c6c935b78ed55f13

Integrations Overview

Compare Jira with other data sources and agent tools.