Available today#
| Action | Description |
|---|---|
| Find matching issues | Search Jira Cloud work using governed connector access |
| Summarize issue state | Review ticket details, comments, and current status |
| Create issues | Open new tracked work from Sidekick |
| Comment on issues | Add bounded updates to existing tickets |
Setup#
- Go to Settings → Connections
- Click Add Connection → Jira
- Authorize through Atlassian OAuth
- Confirm the Jira Cloud site and scopes the workspace should use
How to use it#
Ask for the work you need in plain language:
Show me all high-priority bugs assigned to the backend team
that haven't been updated in the last 7 days.
Sprint reporting#
Ask Sidekick for sprint summaries:
Summarize the current sprint: story points completed vs committed,
unfinished items, and any scope changes since sprint start.
Capability boundary#
Jira ships today as a bounded Jira Cloud v1 connector. For Jira Data Center or custom internal Jira workflows, use an Advanced Custom MCP server instead of expecting the built-in connector to cover every case.
Governance#
| Action | Recommended approval |
|---|---|
| Read issues | Auto-approve |
| Read sprints | Auto-approve |
| Create issues | Require approval |
| Update issues | Require approval |
info The built-in connector targets Jira Cloud. Use Advanced Custom MCP when you need Data Center support or a more specialized Jira surface.