Jira Integration

Connect your Jira workspace to sync issues, comments, and sprint context as agent knowledge.

4 min read

Jira Integration

Connect CoAgentor to your Jira workspace and your agents will have access to your issues, comments, epic context, and sprint information during live meetings — without you having to brief them manually.

What gets synced

When you connect Jira, CoAgentor syncs:

  • Issues — summary, description, status, priority, issue type, assignee, and reporter
  • Comments — all comments on each issue, with author and date
  • Epic and sprint context — epic name, sprint name, and sprint state (Jira Software projects only)
  • Text attachments — plain text, Markdown, CSV, PDF, Word, and Excel files attached to issues

Issues sync automatically every 6 hours. You can also trigger a manual sync at any time from the integrations page.

Connecting Jira

Open the Integrations page →

  1. Scroll to the Jira card and click Connect Jira.
  2. You'll be redirected to Atlassian to authorise CoAgentor. Sign in if prompted.
  3. Atlassian will ask you to grant read access to your Jira issues and user data. Click Accept.
  4. You'll be redirected back to CoAgentor. An initial sync starts automatically in the background.

CoAgentor requests read-only access to your Jira data. It cannot create, edit, or delete issues.

XXX SCREENSHOT: Jira card in connected state showing project picker and JQL filter

Choosing which projects to sync

By default, CoAgentor syncs all projects your Atlassian account can access. To narrow this down:

  1. Open the Jira card on the integrations page.
  2. Click one or more project badges to select them. Selected projects are highlighted in blue.
  3. Leave all projects unselected to sync everything.
  4. Click Save settings — a re-sync starts automatically.

Filtering with JQL

For more precise control, you can supply a JQL (Jira Query Language) clause. This is ANDed with your project filter:

  • status != Done — exclude completed issues
  • priority in (High, Critical) — only high-priority issues
  • assignee = currentUser() — only issues assigned to you
  • updated >= -30d — only issues updated in the last 30 days

Leave the JQL field empty to sync all issues in the selected projects.

JQL reference ↗

Plan limits

| Plan | Issues synced | |------|--------------| | Free | Up to 50 | | Solo | Up to 500 | | Pro | Unlimited |

The limit applies to issues only. Text attachments are not counted against this cap.

Syncing manually

Click Sync now on the Jira card to trigger an immediate sync. This is useful after making significant changes to your Jira board that you want available right away.

Disconnecting

Click Disconnect on the Jira card. All synced issues will be removed from your data sources and any contexts that referenced them. Your actual Jira data is unaffected.

Troubleshooting

My issues aren't appearing in the context builder

The initial sync runs in the background and can take a few minutes depending on the number of issues. Try clicking Sync now and waiting 60 seconds, then refresh.

JQL filter error

If your JQL clause is invalid, the sync will fail silently for that connection. Check your JQL syntax using Jira's issue search before saving it here.

Reconnect needed badge

Atlassian OAuth tokens expire after 90 days of inactivity. If you see a "Reconnect needed" badge, click Reconnect to go through the OAuth flow again. Your sync configuration (projects and JQL) will be preserved.

Sprint fields not showing

Sprint context (customfield_10020) is only available in Jira Software projects. Jira Service Management and Jira Work Management projects don't expose sprint data — issues from those projects will sync without a sprint line.

Related articles

Still have questions?

Our team typically responds within one business day.

Contact us →