Jira integration
Jira integration.
Connect Jira to sync selected projects into your ContextStream workspace. Issues, comments, and sprint data become searchable memory events.
Per-workspace integration
The Jira integration is configured per workspace. Each ContextStream workspace can connect to different Atlassian sites or Jira projects. This allows teams to keep their contexts separate while sharing the same ContextStream organization.
What you get
Jira data, surfaced where you work.
Once connected, your Jira data enriches AI interactions across ContextStream. Here's how it adds value:
01
Automatic Context Enrichment
When you call context_smart or session_smart_search, relevant Jira issues, decisions, and sprint context are automatically included in AI responses. No extra tools needed — your existing prompts become smarter.
Example: Ask "What's blocking the payment feature?" and get blockers extracted from Jira issues without calling any Jira-specific tool.
02
Extracted Knowledge
ContextStream automatically distills decisions, lessons, and insights from your Jira issue descriptions and comments. These become searchable memory that persists across sessions.
Example: Use integration(provider="jira", action="knowledge") to see "We decided to use event sourcing for orders" extracted from ENG-245 comments.
03
Sprint Awareness
ContextStream tracks active sprints, sprint goals, and issue progression. Ask about what's in the current sprint, what's at risk, or what shipped last sprint.
Example: Ask "What's left in the current sprint?" and get a breakdown of remaining issues by status and assignee.
04
Unified Memory
Jira events become memory events alongside your manual captures. Use memory(action="search", ...) or session(action="recall", ...) to find Jira context mixed with your other decisions and notes.
Example: "What do we know about the onboarding flow?" returns your captured decisions AND relevant Jira issue discussions.
Example prompts
Try these in your AI editor.
Try these prompts in your AI editor to see Jira integration in action:
Overview
Project activity as memory.
The Jira integration brings your project management activity into ContextStream, making issues, comments, and sprint data searchable and available as context for your AI tools. Content is synced as memory events that can be retrieved via MCP tools or the search API.
Real-time webhooks
Issues, comments, and status transitions are captured via webhooks as they happen in Jira.
Semantic search
Find issues by meaning, not just keywords. Search across all synced projects instantly.
Sprint tracking
Track sprint progress, goals, and velocity. See what's on track and what's at risk.
Setup guide
Three steps to connect.
01
Connect your Atlassian account
- 01Go to your ContextStream workspace settings and navigate to Integrations.
- 02Click Connect on the Jira card to start the OAuth flow.
- 03Authorize ContextStream to access your Atlassian account. You will be asked to grant access to your Jira Cloud site.
- 04Once connected, the Jira card will show "Connected" status.
02
Select Jira projects to sync
- 01Click Configure on the connected Jira integration.
- 02Browse available projects from your Jira Cloud site.
- 03Select the projects you want to sync. All issue types within selected projects are included.
- 04Optionally, link Jira projects to specific ContextStream projects for organized context retrieval.
03
Initial sync & backfill
- 01After selecting projects, ContextStream will perform an initial sync to import issues, comments, and sprint data. You can configure the backfill depth in the integration settings.
- 02Click Sync Now at any time to trigger an immediate sync of all configured projects.
What gets synced
Synced content types.
| Content type | Details | Metadata captured |
|---|---|---|
| Issues | All issues from configured projects | Title, status, priority, type, assignee, labels, sprint |
| Comments | Issue comments and discussions | Content, author, parent issue reference |
MCP tools (v0.4.x)
Query Jira through MCP.
Access Jira data through the consolidated integration tool available in Claude Code, Cursor, and other MCP-compatible editors.
Use integration(provider="jira", action="...") for Jira-specific queries.
integration(provider="jira", action="stats")Get overview statistics: total issues synced, type breakdown (bugs, stories, tasks, epics), priority distribution, and sync status.
integration(provider="jira", action="issues", project_key="ENG", status="...", priority="...", issue_type="...", assignee="...")List and filter issues. Filter by project key, status (open, in_progress, done), priority, issue type (bug, story, task, epic), and assignee.
integration(provider="jira", action="search", query="...")Search across Jira issues and comments by content. Results ranked by relevance. Sort by relevance, recent, or priority.
integration(provider="jira", action="activity")Get recent activity feed: issue creations, status transitions, comments, and sprint changes. Optionally filter by project and timeframe (days param).
integration(provider="jira", action="knowledge")Get decisions, lessons, and insights automatically extracted from Jira issues and comments. Filter by knowledge type (decision, lesson, fact, insight).
integration(provider="jira", action="summary")Get a high-level summary of Jira activity with sprint progress, key decisions, blockers, and notable changes. Customize timeframe with the days param and optionally scope by project.
integration(provider="jira", action="connected")Check if the Jira integration is connected and return basic connection metadata including the Jira Cloud site URL and sync status.
integration(provider="all", action="team_search", query="...")TeamSearch across Jira, GitHub, Slack, and other connected integrations in a single query. Results ranked by relevance across all sources. Sort by relevance, recent, or engagement.
Dashboard
Jira dashboard.
Access detailed analytics and insights from the Jira dashboard in your workspace settings.
Overview stats
Total issues, bugs, stories, tasks, and epics synced at a glance with priority distribution.
Sprint progress
Active sprint burndown, completion percentage, and at-risk items visualized over time.
Issue breakdown
Issues grouped by type, status, priority, and assignee for quick team visibility.
Project stats
Per-project breakdown of issue counts, resolution rates, and recent activity.
Security & privacy
Built-in safeguards.
OAuth 2.0 authentication
ContextStream uses Atlassian's official OAuth 2.0 (3LO) flow. Your credentials are never stored — only encrypted access tokens.
Minimal scopes
We request only read-only scopes needed for syncing: read:jira-work, read:jira-user. No write access is requested.
Explicit project selection
You choose exactly which Jira projects to sync. No projects are synced by default.
Revoke anytime
Disconnect the integration at any time from your workspace settings. This revokes access and stops all syncing.
Sync behavior
How sync works.
Real-time webhooks
New issues, comments, and status transitions are captured via Jira webhooks as they happen. This provides near-instant sync for new content.
Periodic polling
A background sync runs periodically to catch any missed events and update issue states, sprint assignments, and priority changes.
Manual sync
Click Sync Now in the integration settings to trigger an immediate full sync of all configured projects.
State updates
When issues transition between statuses (e.g., To Do, In Progress, Done), the state is updated in ContextStream automatically.
Troubleshooting
Common issues.
Integration shows "Error" status
This usually means the OAuth token has expired or been revoked. Try disconnecting and reconnecting the integration. If the issue persists, check that you haven't revoked the app authorization in your Atlassian account settings.
Projects not showing up
Make sure you granted access to the correct Jira Cloud site during the OAuth flow. If you have multiple Atlassian sites, you may need to select the correct one. Also verify that your Atlassian account has access to the projects you want to sync.
Search not finding recent issues
New content may take a few minutes to be indexed and searchable. Try clicking Sync Now to force an immediate sync, then search again.
Jira admin approval required
Some Atlassian organizations require admin approval for third-party OAuth apps. Contact your Jira administrator to approve ContextStream access in the Atlassian admin console under Connected Apps.
Next steps
Keep going.
Once connected, Jira issues and comments become Memory Events (source: jira) and are available to your AI tools via MCP.
Back to integrations overview or see GitHub integration.
Jira is a trademark of Atlassian Pty Ltd. ContextStream is not affiliated with, endorsed by, or sponsored by Atlassian Pty Ltd.