Announcing o11's backing from Y Combinator.](/content/blog/announcing-backing-from-y-combinator/index.html)

# AI for Jira

## AI that grooms the backlog with you.

- Run sprint grooming and bulk edits in place.
- Update statuses and fields from natural language.

## Sprint 24

Sprint 24 active · 5 days left

### To do

- Add invite-by-link onboarding flow (ENG-412)
- Index analytics events table by region (ENG-415)
- Refactor billing webhook retry logic (ENG-418)
- Spike: token refresh strategy (ENG-420)

### In progress

- Backfill audit log gaps Apr 18-19 (ENG-405)
- Migrate auth service to NestJS 10 (ENG-403)
- Add CSV export for orders dashboard (ENG-401)

### In review

- Fix p95 latency regression on /search (ENG-394)
- Add health-check endpoint for Snowflake sync (ENG-389)

### Done

- Update SDK docs for v3.4 release (ENG-380)
- Patch flaky CI test on metrics suite (ENG-378)
- Bump nginx to 1.25.4 in prod fleet (ENG-371)

## o11 for Jira: an AI agent layer for the issue tracker

o11 is an AI execution layer that runs inside Jira. The agent grooms backlogs, transitions issues, edits fields, and pushes status updates without sending an engineer or PM into a side panel to retype what they already decided in standup.

If you have searched for **AI for Jira**, a **Jira AI agent**, or an **alternative to Atlassian Intelligence** that actually moves work, the difference comes down to one question: does the AI describe the sprint or run the sprint?

## What teams use o11 for in Jira

- **Sprint grooming.** Re-rank backlog items, set estimates, split epics, and clean stale tickets in a single grooming pass.
- **Issue creation.** Spin up well-formed issues from chats, design reviews, or incident notes — with the right project, type, components, and links.
- **Status updates.** Transition issues, fill in resolution notes, and post sprint health updates without manual data entry.
- **Bulk edits.** Re-assign owners, fix labels, change fix versions, and roll dates across hundreds of issues at once.

## Why o11 differs from Atlassian Intelligence

Atlassian Intelligence ships inside Jira as a content layer — it summarizes issues, suggests next steps, and answers questions in a side panel. The execution still ends with a human transitioning the ticket, editing the field, or filing the next one. o11 is built to drive those clicks. The chat is the control surface, Jira is where the work lands.

## Built for teams that live across systems

Jira is one part of a much larger stack — usually paired with GitHub, Slack, Confluence, and a release tracker. o11 is positioned to act across all of them. A bug filed in Slack can become a properly-typed Jira issue, a draft RFC in Confluence, a branch and PR in GitHub, and a Slack handoff back to the on-call without anyone stitching the tools together by hand.

## Where Jira teams typically start with o11

- **Engineering managers** with sprint grooming and weekly hygiene.
- **PMs** with backlog rewrites, status rollups, and release notes.
- **Program managers** with cross-team rollups and dependency cleanup.
- **On-call engineers** with incident-to-issue conversion and after-action edits.

## How o11 respects Jira permissions

The agent operates with the user’s own account. Project roles, issue security schemes, workflow conditions, and field configurations apply exactly the way they do for that user in the UI. Nothing is bypassed. That is what makes o11 deployable in regulated engineering orgs that cannot trust a tool that runs as an over-privileged service account.

## FAQ

**How is this different from Atlassian Intelligence?**  
Atlassian Intelligence summarizes and suggests; o11 transitions issues and edits fields directly.

**Who is it for?**  
Engineering managers, PMs, and program leads running active sprints.